As you might know, PEP 581 (Using GitHub Issues for CPython) has been
approved. I've been working with Ewa, Ee, the Working Group, the
Steering Council, and the GitHub folks to make this happen, and the SC
encouraged me to give you all a quick update.
This effort is being tracked at
<https://github.com/psf/gh-migration/projects/1>: this board reflects
the current status of the project. The PEPs (including PEP 588 --
GitHub Issues Migration Plan) haven't been updated yet and might
…
[View More]contain outdated information, so please refer to the psf/gh-migration
repo for the latest updates.
During the next phase I will work with the WG to sort out all the
major issues that we might encounter, and then I will once again reach
out to you to gather feedback from the wider audience that follows
these mailing lists.
Best Regards,
Ezio Melotti
[View Less]
Hi. I have an Alpha/OSF machine up and running.
It is little slow, but it works ok.
I would like to run Python3 on it.
I have it "compiling and working". It was easy enough so far.
https://github.com/python/cpython/pull/27063
Admitted, I haven't figured out what is happening with the posixsubprocess module.
Yes? No? Maybe?
I can possibly provide ongoing "support" (I don't expect it will be much) and a buildbot (if really required),
if I can get it working a bit more, if this is approved, …
[View More]etc. I haven't looked yet at what buildbot involves.
Thank you,
- Jay
[View Less]
Hi everyone,
I would like to repeal PEP 509. We don't really have a process for
repealing a PEP. Presumably I would just write another PEP.
Before I do so, I would like to know if anyone thinks we should keep
PEP 509.
The dictionary version number is currently unused in CPython and just
wastes memory. I am not claiming that we will never need it, just that
we shouldn't be required to have it. It should be an internal
implementation detail that we can add or remove depending on …
[View More]requirements.
Thoughts?
Cheers,
Mark.
[View Less]
Python 3.10.0 is almost ready. This release, 3.10.0rc1, is the penultimate
release preview. You can get it here:
https://www.python.org/downloads/release/python-3100rc1/
*This is the first release candidate of Python 3.10*
This release, **3.10.0rc1**, is the penultimate release preview. Entering
the release candidate phase, only reviewed code changes which are
clear bug fixes are allowed between this release candidate and the final
release. The second candidate and the last planned release …
[View More]preview is
currently planned for 2021-09-06 while the official release is planned for
2021-10-04.
There will be no ABI changes from this point forward in the 3.10 series and
the goal is that there will be as few code changes as possible.
*Call to action*
Core developers: all eyes on the docs now
- Are all your changes properly documented?
- Did you notice other changes you know of to have insufficient
documentation?
Community members
We strongly encourage maintainers of third-party Python projects to prepare
their projects for 3.10 compatibilities during this phase. As always,
report any issues to the Python bug tracker <https://bugs.python.org/>.
Please keep in mind that this is a preview release and its use is **not**
recommended for production environments.
*And now for something completely different*
In theoretical physics, quantum chromodynamics (QCD) is the theory of the
strong interaction between quarks and gluons, the fundamental particles
that make up composite hadrons such as the proton, neutron, and pion. The
QCD analog of electric charge is a property called color. Gluons are the
force carrier of the theory, just as photons are for the electromagnetic
force in quantum electrodynamics. There are three kinds of charge in QCD
(as opposed to one in quantum electrodynamics or QED) that are usually
referred to as "color charge" by loose analogy to the three kinds of color
(red, green and blue) perceived by humans. Other than this nomenclature,
the quantum parameter "color" is completely unrelated to the everyday,
familiar phenomenon of color.
*We hope you enjoy those new releases!*
Thanks to all of the many volunteers who help make Python Development and
these releases possible! Please consider supporting our efforts by
volunteering yourself or through organization contributions to the Python
Software Foundation.
Regards from cloudy London,
Your friendly release team,
Pablo Galindo @pablogsal
Ned Deily @nad
Steve Dower @steve.dower
[View Less]