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
Is your feature request related to a problem? Please describe.
I am asking to see what "super old" wxPython version is too old.
This fall, some places that checked for really old wxPython/wxWidgets versions were dropped. Should we be doing the same and only support the wxPython "Phoenix", the 2018 rewrite that we use now?
What active plateforms need a next year latest version of GRASS that doesn't have at least a version 4 of wxPython?
Supporting before and after that project means essentially supporting two different places to import our classes, as some are placed a bit everywhere, and we also special-case some other functions a bit everywhere too
Describe the solution you'd like
Only support wxPython "Phoenix" in the latest main branch (developpement) for future releases, and drop special handling.
Describe alternatives you've considered
Status quo.
Additional context
Some static analysis is harder to do, as some classes have a base class coming from an import done inside a conditional block, and that condition is from another import that is the result of a function call, so no static analysis there. This means that there are multiple "Argument to class must be a base class" that prevent full analysis of available methods in classes.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
I am asking to see what "super old" wxPython version is too old.
This fall, some places that checked for really old wxPython/wxWidgets versions were dropped. Should we be doing the same and only support the wxPython "Phoenix", the 2018 rewrite that we use now?
What active plateforms need a next year latest version of GRASS that doesn't have at least a version 4 of wxPython?
Supporting before and after that project means essentially supporting two different places to import our classes, as some are placed a bit everywhere, and we also special-case some other functions a bit everywhere too
Describe the solution you'd like
Only support wxPython "Phoenix" in the latest main branch (developpement) for future releases, and drop special handling.
Describe alternatives you've considered
Status quo.
Additional context
Some static analysis is harder to do, as some classes have a base class coming from an import done inside a conditional block, and that condition is from another import that is the result of a function call, so no static analysis there. This means that there are multiple "Argument to class must be a base class" that prevent full analysis of available methods in classes.
The text was updated successfully, but these errors were encountered: