-
-
Notifications
You must be signed in to change notification settings - Fork 626
-
-
Notifications
You must be signed in to change notification settings - Fork 626
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update wx for 2024.1 #12551
Comments
wxWidgets/Phoenix#1950 appears not to have been merged. |
Blocking #12064. |
Hi, While the wxPython issue mentioned is a key blocker, I think it would be best to proceed with the workaround for now as Python 3.7 will be end of life in June 2023 (come July 2023, and I think telling people that you need to use a version of Python that's no longer supported by Python Software Foundation can send mixed signals). Also, note that 32-bit wxPython 4.2.0 was not uploaded to Python Package Index, so we need to either create a repo for hosting 32-bit wxPython wheel or let Appveyor build the binary for us. Thanks. |
blocked by wxWidgets/Phoenix#2235, there are no 32bit wheels of wxPython 4.2.0 |
This also blocking updating python to 3.10. Without updating to wxPython 4.2.0 and self-compiling 32bit, we will have to update to Python 3.8 or 3.9. |
We should target 3.11 (slated for late October) provided that dependancies are functional. |
hello @seanbudd |
Hi, 32-bit Python wheels posted on wxPython issue 2235 comment - please give them a try. Thanks. |
@seanbudd Why has the milestone been set to 2024? |
@codeofdusk this and updating python are not scheduled until 2024.1 |
In the case of this issue, there's no known improvements from updating wxPython, and without 32bit wheels on pip, to update for 2023.1, we'd have to design a new system for incorporating the wheel. |
Hi, Actually, you can force Pip to install a wheel from a URL, and I have managed to do just that with a 32-bit wxPython 4.2.0 wheel I built for Python 3.11. If this works, I think we can:
For reference, wxPython 4.2.0 32-bit wheel for Python 3.7 which I built a few days ago can be found at: Thanks. |
If we were to use a custom wheel, we would want it to be built either by NV Access directly (or indirectly via GitHub actions). |
It looks like Bookworm would also be interested in this: josephsl/wxpy32whl#1 |
It would also be ideal to just use official wheels, and avoid picking up this extra maintenance burden. |
Hi, I'll document it in the rpo, but for reference:
Thanks. |
Hi, For now 32-bit buildbots are disabled for wxPython unless Robin finds a way to restore them. Even for 64-bit wheels, Python 3.8 or later is required to obtain official wheels for 4.2.0. There is also an issue with wxPython 4.2.0 where pyd files do not have file extensions if the wheel is built with Python 3.11. In the long-term, I expect packages to drop support for 32-bit after CPython itself drops 32-bit support, and I expect that'll be the case once Windows 10 support ends (as early as 2026 unless Python core developers say 32-bit will be supported for a while longer). Thanks. |
This now unblocked. wxPython 4.2.1 has now been released with Windows wheels wxWidgets/Phoenix#2246 (comment) |
Fixes #15742 Regression from #12551 Summary of the issue: Run NVDA with a touchscreen computer and try tapping on the screen in rapid succession (for example, when invoking an object). The touch gesture fails due to a change in wxPython, where Timer.Start expects integers only, not floats. Description of user facing changes No errors or issues when using touch navigation Description of development approach Add typing to touchTracker to better understand the cause of the issue. Convert the touch emit timer to use an integer
wxPython 4.2.0 has been released. Unlike the previous release, wxPython uses a wxWidgets release (3.2.0), instead of tracking the master branch (wxWidgets 3.1.4.XX) in wxPython 4.1.1.
Based on the changes to wxPython and wxWidgets it appears that there should be no API breaking changes as a result of upgrading to 4.2.0.
The text was updated successfully, but these errors were encountered: