My .ssh key became inactive about a year ago, and I'm looking to
reactivate it; there are some bugfixes that I'd quite like to get in
before Python 3.6.
I've created a new ED25519 key pair, and I emailed the public key to
hgaccounts(a)python.org a few days ago. I didn't get any response, so
I'm not sure if that email went into a black hole or not. Is there
something else I need to do, or is it just a matter of being patient?
On behalf of the Python development community and the Python 3.6 release
team, I'm happy to announce the availability of Python 3.6.0a4. 3.6.0a4
is the last of four planned alpha releases of Python 3.6, the next major
release of Python. During the alpha phase, Python 3.6 remains under
heavy development: additional features will be added and existing
features may be modified or deleted. Please keep in mind that this is a
preview release and its use is not recommended for production environments.
You can find Python 3.6.0a4 here:
The next planned release of Python 3.6 will be 3.6.0b1, currently
scheduled for 2016-09-12. 3.6.0b1 will mark the beginning of the beta
phase of Python 3.6; at that time, feature development for 3.6 will be
complete and the emphasis will change to fixing bugs and regressions.
More information about the release schedule can be found here:
nad(a)python.org -- 
as many here know, the recent comparison of Python/Ruby w.r.t. static analysis
done by viva64.com (PVS-Studio) accidentally included the external packages that
are automatically downloaded in the scripted build (like OpenSSL).
I've notified viva64.com, and they were nice enough to do a second analysis,
this time done with the Linux version of PVS-Studio:
They found another issue. :)
Andrey Karpov has offered a key for PVS-Studio for the Python Team (python.org),
valid for half a year. It's a *single shared key*: We have to keep it secret
and it's obviously only for Python core development.
If you want it, mail me privately -- similar to the MSDN licences.
The next and final alpha snapshot planned for the 3.6 release cycle is coming up soon. Keep in mind that the feature development phase of the 3.6 release cycle is nearing an end. The next major milestone is a big one: the first beta shapshot, 3.6.0b1, scheduled for Monday, 09-12, a little over four weeks from now. That will mark the end of the unrestricted feature development phase and the start of the bugfix/stabilization/testing phase. All feature code for 3.6.0 should be checked in by b1. During the beta phase, the emphasis will be on fixes for new features, fixes for all categories of bugs and regressions, and documentation fixes/updates. After b1, new features should be targeted for 3.7; more details will be forthcoming by b1.
As a reminder, alpha releases are intended to make it easier for the wider community to test the current state of new features and bug fixes for an upcoming Python release as a whole and for us to test the release process. During the alpha phase, features may be added, modified, or deleted up until the start of the beta phase. Alpha users beware!
2016-08-15 ~12:00 UTC: code snapshot for 3.6.0 alpha 4.
now to 2016-09-12: Alpha phase (unrestricted feature development)
2016-09-12: 3.6.0 feature code freeze, 3.7.0 feature development begins
2016-09-12 to 2016-12-04: 3.6.0 beta phase (bug and regression fixes, no new features)
2016-12-04 3.6.0 release candidate 1 (3.6.0 code freeze)
2016-12-16 3.6.0 release (3.6.0rc1 plus, if necessary, any dire emergency fixes)
nad(a)python.org -- 
I've just re-built the latest Python 3.6 from the repo using this:
PYTHONHOME=/usr/local ./configure --with-pydebug && make -s -j2
and I'm getting:
Failed to build these modules:
which means I can't run the test suite:
[steve@ando cpython]$ ./python -m test -j3
Traceback (most recent call last):
File "/home/steve/python/python-dev/cpython/Lib/runpy.py", line 184, in _run_module_as_main
File "/home/steve/python/python-dev/cpython/Lib/runpy.py", line 85, in _run_code
File "/home/steve/python/python-dev/cpython/Lib/test/__main__.py", line 1, in <module>
from test.libregrtest import main
File "/home/steve/python/python-dev/cpython/Lib/test/libregrtest/__init__.py", line 4, in <module>
from test.libregrtest.cmdline import _parse_args, RESOURCE_NAMES
File "/home/steve/python/python-dev/cpython/Lib/test/libregrtest/cmdline.py", line 4, in <module>
from test import support
File "/home/steve/python/python-dev/cpython/Lib/test/support/__init__.py", line 15, in <module>
File "/home/steve/python/python-dev/cpython/Lib/logging/handlers.py", line 26, in <module>
import logging, socket, os, pickle, struct, time, re
File "/home/steve/python/python-dev/cpython/Lib/socket.py", line 52, in <module>
import os, sys, io, selectors
File "/home/steve/python/python-dev/cpython/Lib/selectors.py", line 11, in <module>
ImportError: No module named 'select'
Is it just me? Any suggestions?