python-committers July 2016

python-committers@python.org

13 participants
9 discussions

autoconf 2.70
by Xavier de Gaye 24 Nov '16

24 Nov '16

It seems that the configure file on the default branch has been generated with autoconf 2.70. Autoconf 2.70 has not yet been released [1]. The differences between the generated configure files with 2.69 and 2.70 are a few lines [3] added by 2.70 with 'runstatedir' in them. The last old discussion on the usage of different autoconf versions [2] does not really answer the following question: I am using 2.69, should a commit that changes configure.ac respects the existing 'runstatedir' lines added by a previous commit or uses directly the configure file generated by 2.69 ? Xavier [1] http://thread.gmane.org/gmane.comp.sysutils.autoconf.general/16193 [2] http://thread.gmane.org/gmane.comp.python.devel/135327 [3] diff -r fe168c2b5e95 configure --- a/configure Wed Jul 06 23:58:16 2016 -0700 +++ b/configure Fri Jul 22 14:49:31 2016 +0200 @@ -777,7 +777,6 @@ docdir oldincludedir includedir -runstatedir localstatedir sharedstatedir sysconfdir @@ -888,7 +887,6 @@ sysconfdir='${prefix}/etc' sharedstatedir='${prefix}/com' localstatedir='${prefix}/var' -runstatedir='${localstatedir}/run' includedir='${prefix}/include' oldincludedir='/usr/include' docdir='${datarootdir}/doc/${PACKAGE_TARNAME}' @@ -1141,15 +1139,6 @@ | -silent | --silent | --silen | --sile | --sil) silent=yes ;; - -runstatedir | --runstatedir | --runstatedi | --runstated \ - | --runstate | --runstat | --runsta | --runst | --runs \ - | --run | --ru | --r) - ac_prev=runstatedir ;; - -runstatedir=* | --runstatedir=* | --runstatedi=* | --runstated=* \ - | --runstate=* | --runstat=* | --runsta=* | --runst=* | --runs=* \ - | --run=* | --ru=* | --r=*) - runstatedir=$ac_optarg ;; - -sbindir | --sbindir | --sbindi | --sbind | --sbin | --sbi | --sb) ac_prev=sbindir ;; -sbindir=* | --sbindir=* | --sbindi=* | --sbind=* | --sbin=* \ @@ -1287,7 +1276,7 @@ for ac_var in exec_prefix prefix bindir sbindir libexecdir datarootdir \ datadir sysconfdir sharedstatedir localstatedir includedir \ oldincludedir docdir infodir htmldir dvidir pdfdir psdir \ - libdir localedir mandir runstatedir + libdir localedir mandir do eval ac_val=\$$ac_var # Remove trailing slashes. @@ -1440,7 +1429,6 @@ --sysconfdir=DIR read-only single-machine data [PREFIX/etc] --sharedstatedir=DIR modifiable architecture-independent data [PREFIX/com] --localstatedir=DIR modifiable single-machine data [PREFIX/var] - --runstatedir=DIR modifiable per-process data [LOCALSTATEDIR/run] --libdir=DIR object code libraries [EPREFIX/lib] --includedir=DIR C header files [PREFIX/include] --oldincludedir=DIR C header files for non-gcc [/usr/include]

10 19

Xavier de Gaye
by Victor Stinner 26 Jul '16

26 Jul '16

Hi, 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): https://docs.python.org/devguide/developers.html#permissions-history 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. Great! For Android, the HQ is the "Meta-issue: support of the android platform" https://bugs.python.org/issue26865 Victor

4 3

PEP process with github
by Paul Moore 24 Jul '16

24 Jul '16

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? Paul

5 6

No commits to the devguide, please
by Brett Cannon 22 Jul '16

22 Jul '16

I'm going to try to migrate it to GitHub today.

1 1

[RELEASE] Python 3.6.0a3 is now available
by Ned Deily 12 Jul '16

12 Jul '16

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 production environments. You can find Python 3.6.0a3 here: https://www.python.org/downloads/release/python-360a3/ The next release of Python 3.6 will be 3.6.0a4, currently scheduled for 2016-08-15. --Ned -- Ned Deily nad(a)python.org -- []

1 0

Reminder: 3.6.0a3 shapshot 2016-07-11 12:00 UTC
by Ned Deily 08 Jul '16

08 Jul '16

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. To recap: 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) --Ned https://www.python.org/dev/peps/pep-0494/ -- Ned Deily nad(a)python.org -- []

1 0

generated importlib files modified by the build
by Xavier de Gaye 08 Jul '16

08 Jul '16

The files generated by Programs/_freeze_importlib.c Python/importlib.h Python/importlib_external.h are modified by the build after the last changeset d32517de5d8c (Issue #26972: Fix some mistakes in importlib-related docstrings.). Xavier

2 1

MSDN subscriptions/renewals
by Brian Curtin 07 Jul '16

07 Jul '16

Hey all, 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: First Name: Last Name: Email Address: Project/Company: Python Software Foundation Complete Mailing Address: Phone Number: 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 subscription. Brian

2 1

Is it just me or is the tip broken at the moment?
by Steven D'Aprano 07 Jul '16

07 Jul '16

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://hg@hg.python.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> main() 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 return get_config_vars().get(name) File "/home/steve/python/python-dev/cpython/Lib/sysconfig.py", line 540, in get_config_vars _init_posix(_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' -- Steve

3 3

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

python-committers July 2016