Xavier de Gaye is a Python core developer since June 3, 2016. I just
noticed that his grant wasn't logged in the devguide: it's now fixed
(online doc not up to date yet):
Xavier already pushed some changes to enhance Android support in
CPython 3.6. I helped him to learn the CPython workflow (Mercurial,
bug tracker, etc.).
I consider that he knows understand well the process and I don't need
to mentor him. But I will probably continue to help him to review his
patches, answer to questions, etc.
It looks like the Android port is also related to cross-compilation,
so it looks like CPython 3.6 will be easier to cross-compile as well.
For Android, the HQ is the "Meta-issue: support of the android platform"
With PEPs now being hosted on github, is there any specific process
for handling reviews/discussions on the github tracker? PEP 1 doesn't
mention the matter, other than to note that discussions "may also
occur on a list other than python-dev" although the approach of having
a Discussions-To header doesn't really work well there.
My suggestion (which is basically what we've been doing with PEP 514)
is that PEP discussions are acceptable on the tracker, but comments on
the core list should be monitored as well (and responded to on-list).
When the PEP is ready for acceptance, a posting of the final version
should be made to the list, and the acceptance email should be posted
to the list (so that there's a permanent record of the acceptance,
which can be linked to in the PEP).
Is that reasonable? Does it need an update to PEP 1 to cover it? If
so, should I post a PR for PEP 1? Or is it obvious enough to be
assumed without needing the bureaucracy of updating PEP 1?
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.0a3.
3.6.0a3 is the third 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
You can find Python 3.6.0a3 here:
The next release of Python 3.6 will be 3.6.0a4, currently scheduled for
nad(a)python.org -- 
The next alpha snapshot for the 3.6 release cycle is coming up in a couple of days. This is the third of four alphas we have planned. Keep that feature code coming in!
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!
Looking ahead, the last alpha release, 3.6.0a4, will follow next month on 2016-08-15. This is a slight change from the previous schedule. Due to popular request, we're moved the feature code cutoff date, 3.6.0b1, from Wednesday, 09-07, to Monday, 09-12, to allow a bit more time after the end-of-summer holiday. In doing so, it seems to make sense to move the final alpha back a week to give a bit more time there for check-ins.
2016-07-11 ~12:00 UTC: code snapshot for 3.6.0 alpha 3
2016-08-15 ~12:00 UTC: code snapshot for 3.6.0 alpha 4. (**CHANGED**, was 08-08)
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 (**CHANGED**, was 09-07)
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 -- 
The files generated by Programs/_freeze_importlib.c
are modified by the build after the last changeset d32517de5d8c
(Issue #26972: Fix some mistakes in importlib-related docstrings.).
The fine folks at Microsoft have been giving us complimentary access
to Microsoft Developer Network subscriptions for many years now in
support of Python on Windows, and it's soon going to be expiration
time (or past that) for some of your accounts.
If any existing subscribers anyone would like a renewal, please send
me both your email login as well as your Subscriber ID. You can find
that at https://msdn.microsoft.com/en-us/subscriptions/manage/ once
you're logged in.
If you would like a subscription for the first time, which gives you
access to Visual Studio, Windows disk images, and more, please send me
all of the following:
Project/Company: Python Software Foundation
Complete Mailing Address:
In order to ease the work on our Microsoft contact's side, I'd like to
batch up the list of names that we send them, so I'm going to collect
responses for a week or so and then send them off. After that it takes
around a week for them to go through it and get everything enabled,
after which Microsoft will send you an email about your new
I'm wondering if I've broken something at my end, or if everyone is
seeing the same error.
[steve@ando cpython]$ hg fetch
pulling from ssh://firstname.lastname@example.org/cpython
searching for changes
no changes found
[steve@ando cpython]$ hg update
0 files updated, 0 files merged, 0 files removed, 0 files unresolved
[steve@ando cpython]$ ./python
Failed to import the site module
Traceback (most recent call last):
File "/home/steve/python/python-dev/cpython/Lib/site.py", line 571, in <module>
File "/home/steve/python/python-dev/cpython/Lib/site.py", line 557, in main
known_paths = addusersitepackages(known_paths)
File "/home/steve/python/python-dev/cpython/Lib/site.py", line 281, in addusersitepackages
user_site = getusersitepackages()
File "/home/steve/python/python-dev/cpython/Lib/site.py", line 257, in getusersitepackages
user_base = getuserbase() # this will also set USER_BASE
File "/home/steve/python/python-dev/cpython/Lib/site.py", line 247, in getuserbase
USER_BASE = get_config_var('userbase')
File "/home/steve/python/python-dev/cpython/Lib/sysconfig.py", line 591, in get_config_var
File "/home/steve/python/python-dev/cpython/Lib/sysconfig.py", line 540, in get_config_vars
File "/home/steve/python/python-dev/cpython/Lib/sysconfig.py", line 411, in _init_posix
_temp = __import__(name, globals(), locals(), ['build_time_vars'], 0)
ImportError: No module named '_sysconfigdata_dm'