![]() Of course, there’s always another bug fix release in the future, but given a 12-month window between major releases, lots of new code will get written but not extensively used. Python 3.10.0 was released in October 2021.ģ.10.1 was released 2 months later, with a long list of bugfixes. If you’re using Conda-Forge, the Python 3.11 rollout happens pretty quickly.Ī lot of it is automated, one of the benefits of Conda-Forge over PyPI, so as long as the underlying packages already support 3.11, it should happen pretty quickly now that it’s happening. Given many Python packages are maintained by volunteers with limited free time and working independently, it just takes time for updates to percolate through the system. So there was a tree of dependencies blocking a new release. porting the Sciagraph performance and memory profiler took a couple of months because of some of the major changes to Python’s internals.Įven if the code is compatible, if dependencies aren’t compatible that can still delay a release.įor example, when I started porting the Fil to 3.10, I couldn’t do a release because the test suite relied on the numexpr package, and numexpr wouldn’t release 3.10 wheels until NumPy had complete 3.10 wheels, which didn’t happen immediately. The Python 3.11 support for the Numba project, for example, is still a work-in-progress as of Dec 8, 2022.Īpparently it took them 6 months post-release until they had Python 3.9 support, and 3 months after 3.10.įor my own projects, some should just work, but e.g. In other cases, however, the code is incompatible and requires some work to support new Python releases. That means you can can compile it yourself, with enough work, and if not the maintainer will usually release a new wheel pretty quickly. Sometimes supporting a new release is just a matter of recompiling the code. Older versions might not support the binary wheels for 3.11 on Linux, and instead pip will try to build from source. Important: Make sure you upgrade pip before using it. Some projects required writing code to support changed APIs in Python internals, but will eventually get released-we’ll cover that next. Personally I had branches ready for some of my own projects to build 3.11 wheels, but didn’t do any releases in advance because GitHub Actions’ release candidate Python versions are just different to sometimes make life difficult. For 3.11, wheels were available for all platforms even before 3.11 was released.For 3.10, it had a Linux wheel available the day of 3.10’s release, but not macOS and Windows, which took a bit longer. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |