RE: https://fosstodon.org/@savannah/116416941269710052
This is really good! There's a lot going on in CPython, here's just a few highlights.
#Python #CPython #CoreDispatch
| Blog | https://hugovk.dev |
| GitHub | https://github.com/hugovk |
Hugo van Kemenade
@hugovk
- 1.8K Followers
- 511 Following
- 6.3K Posts
Python 3.14 & 3.15 release manager, core developer, Sovereign Tech Fellow, PSF Fellow, open-source maintainer, PEP editor, NaNoGenMo organiser, winter bicycler
Core DispatchThe SC accepted a PEP that establishes a new Packaging Council, the incremental GC is being reverted, Łukasz Langa is stepping down as Developer in Residence, Rust for CPython has a new progress update, four new PEPs — all this and more in this edition of Core Dispatch.
emmatypingPEP 772, creating an official Python packaging council, has been approved! 🎉
I'm so excited for the council and the work it will do. Many thanks to @pradyunsg, Deb Nicholson, and Barry Warsaw for your hard work in making this happen!
https://discuss.python.org/t/pep-772-packaging-council-governance-process-round-3/100181/118
PEP 772: Packaging Council governance process (Round 3)
The Python Steering Council is happy to accept PEP 772, establishing a Python Packaging Council with broad delegated authority over packaging standards, tools, and implementations. This is the final step in the special approval process for this PEP, which has obtained the approval of the PSF Board, the PyPA, and now, the PSC. Congratulations and thank you to everyone who participated in discussions in person and online! We are excited to see the Python packaging ecosystem move on to its next p...
🗞️ We're going to revert the incremental garbage collector in Python 3.14 and 3.15. See here for details: https://discuss.python.org/t/reverting-the-incremental-gc-in-python-3-14-and-3-15/107014
#Python #Python314 #Python315
#Python #Python314 #Python315
Reverting the incremental GC in Python 3.14 and 3.15
Python 3.14 shipped with a new incremental garbage collector. However, we’ve had a number of reports of significant memory pressure in production environments. We’ve decided to revert it in both 3.14 and 3.15, and go back to the generational GC from 3.13. 3.15 is still in alpha, so such changes are fine. For 3.14, it is unusual for a patch release, but the old GC is a known quantity, the new incremental GC didn’t go through the PEP process, and was rolled back just before the final release of ...
Mike Fiedler, Code GardenerRE: https://fosstodon.org/@pypi/116414611218430369
It's still awesome to me that I get to work on some really hard problems for the common good. This was a lot of work, hope you enjoy the read!
Ned BatchelderOMG! Finally!! In Python 3.15, PYTHONWARNINGS can have real regexes to control warnings: https://docs.python.org/3.15/library/warnings.html#the-warnings-filter.
Discovered by spelunking the Python source while trying to find a way around this warning that I can't ignore: https://github.com/eventlet/eventlet/issues/1089
Nick FUnexpected new single from Massive Attack + Tom Waits!!!
Massive Attack, Tom Waits - Boots on the Ground
Python PEPsPEP 832: Virtual environment discovery
PEP 832 – Virtual environment discovery | peps.python.org
This PEP sets out to help make the discovery of a project’s virtual environment easier for tools by providing a default location as well as a way for a project to point to its preferred virtual environment when it differs from the default location.
Achim Domma
Brett CannonPEP 832: virtual environment discovery
https://discuss.python.org/t/106998
@pauleveritt and the PyCharm folks would probably be interested in this one.
This PEP also puts me in a tie with @vstinner for being the 4th most prolific PEP (co-)author. 😅
PEP 832: virtual environment discovery
The abstract: This PEP sets out to help make the discovery of a project’s virtual environment easier for tools by providing a default location as well as a way for a project to point to its preferred virtual environment when it differs from the default location. This is not a packaging PEP due to the proposed changes to venv and dev workflow stuff like this is ambiguous with no WG to specifically go to. I acknowledge that the PEP targets Python 3.15 and the chances of getting a discussion...