Mailman 3 August 2016 - python-committers

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

Restoring hg.python.org access?
by Mark Dickinson 18 Aug '16

18 Aug '16

Hi all, 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? :-) Thanks, Mark

2 2

{RELEASE] Python 3.6.0a4 is now available
by Ned Deily 16 Aug '16

16 Aug '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.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: https://www.python.org/downloads/release/python-360a4/ 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: https://www.python.org/dev/peps/pep-0494/ --Ned -- Ned Deily nad(a)python.org -- []

1 0

PVS-Studio licences
by Stefan Krah 14 Aug '16

14 Aug '16

Hello, 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: http://www.viva64.com/en/b/0418/ 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. Stefan Krah

2 2

Reminder: 3.6.0a4 snapshot 2016-08-15 12:00 UTC
by Ned Deily 13 Aug '16

13 Aug '16

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

1 0

Failed to build select
by Steven D'Aprano 08 Aug '16

08 Aug '16

Hi, 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: select 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 "__main__", mod_spec) File "/home/steve/python/python-dev/cpython/Lib/runpy.py", line 85, in _run_code exec(code, run_globals) 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> import logging.handlers 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> import select ImportError: No module named 'select' Is it just me? Any suggestions? -- Steve

5 6