[Bug python/28821] New: use mypy type annotations

[Bug python/28821] New: use mypy type annotations

[tromey at sourceware dot org]

https://sourceware.org/bugzilla/show_bug.cgi?id=28821

            Bug ID: 28821
           Summary: use mypy type annotations
           Product: gdb
           Version: 11.1
            Status: NEW
          Severity: normal
          Priority: P2
         Component: python
          Assignee: unassigned at sourceware dot org
          Reporter: tromey at sourceware dot org
  Target Milestone: ---

It might be nice if gdb's Python API supplied mypy type annotations.
See http://mypy-lang.org/
Maybe this can be done via stub files:
https://mypy.readthedocs.io/en/latest/stubs.html

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug python/28821] use mypy type annotations

[fasching.a91 at gmail dot com]

https://sourceware.org/bugzilla/show_bug.cgi?id=28821

Alexander Fasching <fasching.a91 at gmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |fasching.a91 at gmail dot com

--- Comment #1 from Alexander Fasching <fasching.a91 at gmail dot com> ---
I think stubs should be added to typeshed instead of maintaining them in the
GDB project:
https://github.com/python/typeshed

New mypy releases would then include them, so it's not necessary to mess with
mypy settings and updates would be much faster.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug python/28821] use mypy type annotations

[tromey at sourceware dot org]

https://sourceware.org/bugzilla/show_bug.cgi?id=28821

--- Comment #2 from Tom Tromey <tromey at sourceware dot org> ---
Adding them to an external project seems like it would have some
drawbacks.  They'd have to be maintained separately from gdb itself,
and it seems like there would be some version skew.

Is there a problem with maintaining them in gdb?
Actually I was wondering if we could use some technique
to ensure that they have to be up-to-date in the gdb tree,
like generating code from some kind of .def file or the like.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug python/28821] use mypy type annotations

[fasching.a91 at gmail dot com]

https://sourceware.org/bugzilla/show_bug.cgi?id=28821

--- Comment #3 from Alexander Fasching <fasching.a91 at gmail dot com> ---
You are probably right.
Maintaining it in GDB also avoids problems with different versions.

I was initially thinking about the update process. Mypy and typeshed are
updated quite often, so this would also apply for the annotations. The
annotations aren't too complicated though, so this is only a minor concern once
they are good enough.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug python/28821] use mypy type annotations

[tromey at sourceware dot org]

https://sourceware.org/bugzilla/show_bug.cgi?id=28821

--- Comment #4 from Tom Tromey <tromey at sourceware dot org> ---
I hadn't considered changes in mypy -- that's a good point.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug python/28821] use mypy type annotations

[tromey at sourceware dot org]

https://sourceware.org/bugzilla/show_bug.cgi?id=28821

Tom Tromey <tromey at sourceware dot org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |FIXED
             Status|NEW                         |RESOLVED

--- Comment #5 from Tom Tromey <tromey at sourceware dot org> ---
These are in typeshed now:

https://github.com/python/typeshed/tree/master/stubs/gdb

-- 
You are receiving this mail because:
You are on the CC list for the bug.