Go get it here: https://www.python.org/downloads/release/python-390a1/ <https://www.python.org/downloads/release/python-390a1/>
This is an early developer preview of Python 3.9
Python 3.9 is still in development. This releasee, 3.9.0a1 is the first of six planned alpha releases. Alpha releases are intended to make it easier to test the current state of new features and bug fixes and to test the release process. During the alpha phase, features may be added up until the start of the beta phase (2020-05-18) and, if necessary, may be modified or deleted up until the release candidate phase (2020-08-10). Please keep in mind that this is a preview release and its use is not recommended for production environments.
Major new features of the 3.9 series, compared to 3.8
Many new features for Python 3.9 are still being planned and written. Among the new major new features and changes so far:
PEP 602 <https://www.python.org/dev/peps/pep-0602/>, Python adopts a stable annual release cadence
BPO 38379 <https://bugs.python.org/issue38379>, garbage collection does not block on resurrected objects;
BPO 38692 <https://bugs.python.org/issue38692>, os.pidfd_open added that allows process management without races and signals;
A number of standard library modules (audioop, ast, grp, _hashlib, pwd, _posixsubprocess, random, select, struct, termios, zlib) are now using the stable ABI defined by PEP 384 <https://www.python.org/dev/peps/pep-0384/>.
(Hey, fellow core developer, if a feature you find important is missing from this list, let Łukasz know <mailto:email@example.com>.)
The next pre-release of Python 3.9 will be 3.9.0a2, currently scheduled for 2019-12-16.
Replying to python-committers for visibility, although maybe python-dev
would be better.
That's not a "strange non-ASCII character"! That's a form feed
(control-L), definitely defined by ASCII.
There are plenty of these in the code. Some people (who won't be named,
but match the regex "Barry") like them. I don't think we should start
On 11/18/2019 1:40 PM, Tal Einat wrote:
> commit: bcc1cc5cc38b57ac55cbe710849374258d610a08
> branch: master
> author: Tal Einat <taleinat+github(a)gmail.com>
> committer: GitHub <noreply(a)github.com>
> date: 2019-11-18T20:39:47+02:00
> remove a strange non-ASCII character in _iomodule.c (GH-17239)
> M Modules/_io/_iomodule.c
> diff --git a/Modules/_io/_iomodule.c b/Modules/_io/_iomodule.c
> index 5932363f3af35..778b56d475ee5 100644
> --- a/Modules/_io/_iomodule.c
> +++ b/Modules/_io/_iomodule.c
> @@ -503,7 +503,7 @@ _io_open_code_impl(PyObject *module, PyObject *path)
> return PyFile_OpenCodeObject(path);
> * Private helpers for the io module.
> Python-checkins mailing list
The nomination period for the next steering council vote will begin
November 1 AoE* and will end November 15 AoE*.
Open: 2019-11-01 00:00:00 AoE (2019-11-01 08:00:00 EDT)
Close: 2019-11-16 00:00:00 AoE (2019-11-16 07:00:00 EDT)
On November 1, the Discourse category for nominations (
https://discuss.python.org/c/users/steering-council-nominations) will open
Core developers: please be sure to check your email address in
https://github.com/python/voters/blob/master/python-core.toml to ensure you
are listed with your desired email address set in the voting_address field.
This is where ballots will be sent to eligible voters when the vote begins.
Please note that this has changed, previously a .voters.csv file held these
Voting begins December 1st and ends December 15th.
The steering council was asked to address the idea of code ownership in the
project, and so we wanted to publicly state that we view everything as
communally owned by everyone on the development team. That means no one has
exclusive control over any part of the code base.
Having said that, we do recognize that there are experts who should be
consulted as appropriate for various parts of the project. Their expertise
should be listened to and weighed appropriately. But if there is a
disagreement you can always appeal to the steering council to help in
resolving the issue.
The council doesn't view this as a policy shift, just reiterating a
pre-existing one. We also just wanted to emphasize that the steering
council can act as arbitrator if a disagreement arises.
On behalf of the Python development community, I'm slightly chagrined to
announce the availability of Python 3.5.9. There were no new changes in
version 3.5.9; 3.5.9 was released only because of a CDN caching problem,
which resulted in some users downloading a prerelease version of the
3.5.8 .xz source tarball. Apart from the version number, 3.5.9 is
identical to the proper 3.5.8 release.
This new version is a source-only release.
You can find Python 3.5.9 here: