You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've been looking around to try to improve typing of wxPython, trying to build myself. I'm aware of #2651, #1253, and #2468. What would help me a bit, is to have the Python version support policy documented somewhere, to know what typing features can be used, or other language features, and other build requirements. Do you only support non-eol Python versions, meaning 3.9 is the minimum, and has less than a year left, or you go more the SPEC 0 way, like numpy, scipy and more, with a time based approach with less Python versions supported.
As for building, for now, I'm only successful to run builds through CI, not locally. Locally I've manually changed my pyi files + wx sites-packages folder, and had good(er) results by using the sip-generated pyi files and the classes there as base classes for the wx PI generator generated classes. It allowed for more precise types for arguments, but not as much for return types that were none.
The text was updated successfully, but these errors were encountered:
I've been looking around to try to improve typing of wxPython, trying to build myself. I'm aware of #2651, #1253, and #2468. What would help me a bit, is to have the Python version support policy documented somewhere, to know what typing features can be used, or other language features, and other build requirements. Do you only support non-eol Python versions, meaning 3.9 is the minimum, and has less than a year left, or you go more the SPEC 0 way, like numpy, scipy and more, with a time based approach with less Python versions supported.
https://devguide.python.org/versions/
https://scientific-python.org/specs/spec-0000/
As for building, for now, I'm only successful to run builds through CI, not locally. Locally I've manually changed my pyi files + wx sites-packages folder, and had good(er) results by using the sip-generated pyi files and the classes there as base classes for the wx PI generator generated classes. It allowed for more precise types for arguments, but not as much for return types that were none.
The text was updated successfully, but these errors were encountered: