steering-council
nogil-3.12
| steering-council | nogil-3.12 | |
|---|---|---|
| 3 | 3 | |
| 153 | 142 | |
| 1.3% | - | |
| 6.9 | 6.9 | |
| 3 months ago | 5 months ago | |
| Makefile | Python | |
| - | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
steering-council
-
Our Plan for Python 3.13
GVR called it a fork two weeks ago in his justification for not accepting it [1]. If that surprises you, the backstory is summarized pretty well in the article [2] and FAQ [3].
I'm really not trying to be secretive. We can debate whatever you want, but we have to at least acknowledge CPython's stated position.
[1] https://github.com/python/steering-council/issues/188#issuec...
[2] https://www.artima.com/weblogs/viewpost.jsp?thread=214235
[3] https://docs.python.org/3/faq/library.html#can-t-we-get-rid-...
-
Python PEP for Making the GIL Optional Doesn't Get Enough Support
Thanks for reviewing the PEP. The PEP was posted five months ago, and it has been 20 months since an end-to-end working implementation (that works with a large number of extensions) was discussed on python-dev. I appreciate everyone who has taken the time to review the PEP and offer comments and suggestions.
You wrote that the Steering Council's decision does not mean "no," but the steering council has not set a bar for acceptance, stated what evidence is actually needed, nor said when a final decision will be made. Given the expressed demand for PEP 703, it makes sense to me for the steering committee to develop a timeline for identifying the factors it may need to consider and for determining the steps that would be required for the change to happen smoothly.
Without these timelines and milestones in place, I would like to explain that the effect of the Steering Council's answer is a "no" in practice. I have been funded to work on this for the past few years with the milestone of submitting the PEP along with a comprehensive implementation to convince the Python community. Without specific concerns or a clear bar for acceptance, I (and my funding organization) will have to treat the current decision-in-limbo as a “no” and will be unable to pursue the PEP further.
Github Link: https://github.com/python/steering-council/issues/188#issuec...
-
PEP 681 – Data Class Transforms (accepted)
Hmm, likely because it was already submitted to the steering council since April and because the addition is relatively trivial (at runtime, it's almost a no-op).
nogil-3.12
-
The GIL can now be disabled in Python's main branch
Those links are both fairly old. See PEP 703 [0] and Sam’s nogil-3.12 repo [1] for more current versions.
[0] https://peps.python.org/pep-0703/
[1] https://github.com/colesbury/nogil-3.12
- Meta pledges Three-Year sponsorship for Python if GIL removal is accepted
- Our Plan for Python 3.13
What are some alternatives?
full-speed-python - Full Speed Python: a book for self-learners
nogil - Multithreaded Python without the GIL
opensergo-specification - Universal cloud-native microservice governance specification (微服务治理标准)
ideas4 - An Additional 100 Ideas for Computing https://samsquire.github.io/ideas4/
pex - A tool for generating .pex (Python EXecutable) files, lock files and venvs.
codemod - Codemod is a tool/library to assist you with large-scale codebase refactors that can be partially automated but still require human oversight and occasional intervention. Codemod was developed at Facebook and released as open source.
ideas
ideas5 - Batch 5 of Ideas for Computing
Filestash - 🦄 A modern web client for SFTP, S3, FTP, WebDAV, Git, Minio, LDAP, CalDAV, CardDAV, Mysql, Backblaze, ...
PyO3 - Rust bindings for the Python interpreter