Mailman 3 January 2011 - python-committers

anyone still have access to the coverity scan results?
by Brett Cannon 20 Aug '12

20 Aug '12

Access to the Python results is currently down, but has anyone actually accessed the Coverity scan results any time recently? Or who even has access anymore?

9 20

py3k frozen for rc2
by Georg Brandl 13 Feb '11

13 Feb '11

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Okay, this is it: please no more commits to the py3k branch for now. Also, for the remainder of the time until final, please make sure there is an issue for each change you want to make containing the patch (which was already the case for almost all changes after rc1 anyway), and assign the issue to me for sign-off after review. Changes to the "What's new" are exempt, but I would love some volunteers to read through the document and note any issues or typos. cheers, Georg -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.17 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk1FNM4ACgkQN9GcIYhpnLB20wCfUHDP6xAy3jOj2egp+IsYhA8r fYkAnR5gSiXv79y7UXLH97zpcUMcAXHV =4g0D -----END PGP SIGNATURE-----

6 10

[RELEASED] Python 3.2 rc 2
by Georg Brandl 31 Jan '11

31 Jan '11

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On behalf of the Python development team, I'm quite happy to announce the second release candidate of Python 3.2. Python 3.2 is a continuation of the efforts to improve and stabilize the Python 3.x line. Since the final release of Python 2.7, the 2.x line will only receive bugfixes, and new features are developed for 3.x only. Since PEP 3003, the Moratorium on Language Changes, is in effect, there are no changes in Python's syntax and built-in types in Python 3.2. Development efforts concentrated on the standard library and support for porting code to Python 3. Highlights are: * numerous improvements to the unittest module * PEP 3147, support for .pyc repository directories * PEP 3149, support for version tagged dynamic libraries * PEP 3148, a new futures library for concurrent programming * PEP 384, a stable ABI for extension modules * PEP 391, dictionary-based logging configuration * an overhauled GIL implementation that reduces contention * an extended email package that handles bytes messages * a much improved ssl module with support for SSL contexts and certificate hostname matching * a sysconfig module to access configuration information * additions to the shutil module, among them archive file support * many enhancements to configparser, among them mapping protocol support * improvements to pdb, the Python debugger * countless fixes regarding bytes/string issues; among them full support for a bytes environment (filenames, environment variables) * many consistency and behavior fixes for numeric operations For a more extensive list of changes in 3.2, see http://docs.python.org/3.2/whatsnew/3.2.html To download Python 3.2 visit: http://www.python.org/download/releases/3.2/ Please consider trying Python 3.2 with your code and reporting any bugs you may notice to: http://bugs.python.org/ Enjoy! - -- Georg Brandl, Release Manager georg at python.org (on behalf of the entire python-dev team and 3.2's contributors) -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) iEYEARECAAYFAk1Gj6IACgkQN9GcIYhpnLC53wCfcZhc6bxbc+fsmi+PAJxM6npr Hh4An3QRdeyKHm+L3CqVk+EX02PxNx2r =sTu6 -----END PGP SIGNATURE-----

1 0

Re: [python-committers] Issue #11051: system calls per import
by Georg Brandl 30 Jan '11

30 Jan '11

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Am 30.01.2011 13:52, schrieb Nick Coghlan: > On Sun, Jan 30, 2011 at 7:25 PM, Georg Brandl <georg(a)python.org> wrote: >>> And why it does test with and without "module". >> >> Because it always did (there's a thing called backwards compatibility.) >> >> This is of course probably the obvious one to start a deprecation process. > > But why do we check the long suffix for the *new* extension module > naming variants from PEP 3149 and PEP 384? Those are completely new, > so there's no backwards compatibility argument there. It's for easy transition I guess -- you take the same module name and just tack on .abi3.so instead of .so. Georg -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.17 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk1FbB8ACgkQN9GcIYhpnLC6qwCghvhPM1bMaNgmB8SUEoe73vzV DP0AnjKDxrR6Y59uFtSRzmWA+qtvBViA =8H8+ -----END PGP SIGNATURE-----

1 0

rc2 freeze due in two days
by Georg Brandl 29 Jan '11

29 Jan '11

Hi guys, this is just a heads-up that I'll be freezing py3k for the rc2 release in a bit less than 48 hours -- Sunday morning in CET. Please get all changes that you already know are necessary reviewed and committed *before* that: the goal is zero commits between rc2 and final (although I know it's unlikely to be reached) -- or rather the necessity of an rc3 depends on how stable rc2 proves to be. cheers, Georg

12 22

py3k unfrozen, however
by Georg Brandl 17 Jan '11

17 Jan '11

The rc is out. Let's hope for some decent developer testing and bug reports before it's too late... To ensure stability in the py3k branch, I want to enforce strict discipline for commits from now to the release. Any change needs to be reviewed by at least one other core developer (and I mean real reviews, with the committer name mentioned in the commit message). Absolutely no new features or API changes. If in doubt, please consult with this list, or ask me directly. cheers, Georg

1 1

[RELEASED] Python 3.2 rc 1
by Georg Brandl 16 Jan '11

16 Jan '11

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On behalf of the Python development team, I'm very happy to announce the first release candidate of Python 3.2. Python 3.2 is a continuation of the efforts to improve and stabilize the Python 3.x line. Since the final release of Python 2.7, the 2.x line will only receive bugfixes, and new features are developed for 3.x only. Since PEP 3003, the Moratorium on Language Changes, is in effect, there are no changes in Python's syntax and built-in types in Python 3.2. Development efforts concentrated on the standard library and support for porting code to Python 3. Highlights are: * numerous improvements to the unittest module * PEP 3147, support for .pyc repository directories * PEP 3149, support for version tagged dynamic libraries * PEP 3148, a new futures library for concurrent programming * PEP 384, a stable ABI for extension modules * PEP 391, dictionary-based logging configuration * an overhauled GIL implementation that reduces contention * an extended email package that handles bytes messages * a much improved ssl module with support for SSL contexts and certificate hostname matching * a sysconfig module to access configuration information * additions to the shutil module, among them archive file support * many enhancements to configparser, among them mapping protocol support * improvements to pdb, the Python debugger * countless fixes regarding bytes/string issues; among them full support for a bytes environment (filenames, environment variables) * many consistency and behavior fixes for numeric operations For a more extensive list of changes in 3.2, see http://docs.python.org/3.2/whatsnew/3.2.html To download Python 3.2 visit: http://www.python.org/download/releases/3.2/ Please consider trying Python 3.2 with your code and reporting any bugs you may notice to: http://bugs.python.org/ Enjoy! - -- Georg Brandl, Release Manager georg at python.org (on behalf of the entire python-dev team and 3.2's contributors) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) iEYEARECAAYFAk0yn1QACgkQN9GcIYhpnLDTdACgqQYW5ZmTLlxmppBZItprSj7I TmAAn13lgnu9TdVy0Jln7VwOt5JW9CwL =VZ3p -----END PGP SIGNATURE-----

1 0

Freezing py3k for rc1
by Georg Brandl 15 Jan '11

15 Jan '11

Endly, the time is right for rc1. Please coordinate in #python-dev if you need something to go in before. Georg

1 0

New contributors, don't forget to send in a contributor form!
by Brett Cannon 13 Jan '11

13 Jan '11

As I am writing the part of the devguide covering getting commit privs, I figured it was a good thing to send out an email for our new committers to remind them to send in a contributor form: http://www.python.org/psf/contrib/ ASAP.

2 2

Public SSH key for svn
by Eli Bendersky 10 Jan '11

10 Jan '11

Hello, Nick instructed me to send the SSH key here, so here it is. I generated it following the dev FAQ, hopefully it's OK. Eli

2 1