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
It would be good to update, but we need to be sure that all packages we use made a Python 3.9 compatible release. They should be mostly compatible, but it would still be good to avoid issues such as #877 . Also Cython is not forward compatible for packages that include the Cythonized sources in .tar.gz
Can you make another checklist for this? Probably Python 3.9 is still too newly released. It was released in October, so maybe give six months for packages to add support for it and try to update in April?
Something we can look into for 0.18.0. The constraint is not so much that packages won't support 3.9 or 3.10 (they usually would mostly without changes) but that for packages released some time ago there might not be binary wheels on PyPi for those python versions.
Which is important if you want to share objects as pickles between native python and Pyodide. So we should probably make an automated summary of packages that have wheels for the the python version we ship.
It would be good to add a list of instructions for migrating between versions of Python to the development docs when we do this, in interest of explicitly documenting maintenance procedures.
libiconv not found
pyb2d not found
libxml not found
libxslt not found
cffi_example not found
fpcast-test not found
libyaml not found
sharedlib-test not found
zlib not found
CLAPACK not found
micropip not found
sharedlib-test-py not found
nlopt only has Python 3.9 wheels
pyodide-interrupts only has Python 3.9 wheels
numcodecs only has Python 3.9 wheels
msgpack is ready!
python-sat is ready!
MarkupSafe is ready!
pyrsistent is ready!
traits is ready!
pyerfa is ready!
iminuit is ready!
cffi is ready!
biopython is ready!
sqlalchemy is ready!
regex is ready!
wrapt is ready!
numpy is ready!
yt is ready!
scikit-image is ready!
pillow is ready!
kiwisolver is ready!
matplotlib is ready!
pyyaml is ready!
pywavelets is ready!
pydantic is ready!
statsmodels is ready!
astropy is ready!
lxml is ready!
scipy is ready!
scikit-learn is ready!
pandas is ready!
swiglpk is ready!
Thanks for the investigation, @henryiii! It looks like most of the packages in Pyodide supports Python 3.10. I think we could start a discussion of uprading our Python version before long.
Activity
rth commentedon Dec 31, 2020
It would be good to update, but we need to be sure that all packages we use made a Python 3.9 compatible release. They should be mostly compatible, but it would still be good to avoid issues such as #877 . Also Cython is not forward compatible for packages that include the Cythonized sources in .tar.gz
hoodmane commentedon Dec 31, 2020
Can you make another checklist for this? Probably Python 3.9 is still too newly released. It was released in October, so maybe give six months for packages to add support for it and try to update in April?
rth commentedon Apr 18, 2021
Something we can look into for 0.18.0. The constraint is not so much that packages won't support 3.9 or 3.10 (they usually would mostly without changes) but that for packages released some time ago there might not be binary wheels on PyPi for those python versions.
Which is important if you want to share objects as pickles between native python and Pyodide. So we should probably make an automated summary of packages that have wheels for the the python version we ship.
hoodmane commentedon May 12, 2021
It would be good to add a list of instructions for migrating between versions of Python to the development docs when we do this, in interest of explicitly documenting maintenance procedures.
rth commentedon May 12, 2021
Yes, maybe as a subsection of
development/updating-packages.htmlwhere we should also move https://pyodide.org/en/latest/development/contributing.html#migrating-patcheshenryiii commentedon Feb 17, 2022
FYI, here's a quick n'dirty snippet to see what the current status is, using pipx & Python 3.10:
henryiii commentedon Feb 17, 2022
More fun, uh, I mean faster:Still irritated by the boilerplate required to use asyncio in a normal file, vs. pyodide or iPython shells, or
python -m asyncio.ryanking13 commentedon Feb 18, 2022
Thanks for the investigation, @henryiii! It looks like most of the packages in Pyodide supports Python 3.10. I think we could start a discussion of uprading our Python version before long.
hoodmane commentedon Feb 18, 2022
pyodide-interruptswe can just remove, we have a better version of that functionality withpyodide.setInterruptBuffer.hoodmane commentedon Feb 18, 2022
Ideally we should open a new issue about updating to Python 3.10 rather than discussing it here though...
rth commentedon Feb 19, 2022
Opened #2190 about updating to Py3.10.