Mailman 3 August 2013 - python-committers

Inconsistency in Mercurial repository
by Jesus Cea Aug. 19, 2013

Aug. 19, 2013

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Pristine clone from http://hg.python.org/cpython/ """ [jcea@babylon5 cpython]$ hg verify checking changesets checking manifests crosschecking files in changesets and manifests checking files 9928 files, 85259 changesets, 188148 total revisions [jcea@babylon5 cpython]$ hg verify -v repository uses revlog format 1 checking changesets checking manifests crosschecking files in changesets and manifests checking files warning: copy source of 'Modules/_threadmodule.c' not in parents of 60ad83716733 warning: copy source of 'Objects/bytesobject.c' not in parents of 64bb1d258322 warning: copy source of 'Objects/stringobject.c' not in parents of 357e268e7c5f 9928 files, 85259 changesets, 188148 total revisions 3 warnings encountered! """ - -- Jesús Cea Avión _/_/ _/_/_/ _/_/_/ jcea(a)jcea.es - http://www.jcea.es/ _/_/ _/_/ _/_/ _/_/ _/_/ Twitter: @jcea _/_/ _/_/ _/_/_/_/_/ jabber / xmpp:jcea@jabber.org _/_/ _/_/ _/_/ _/_/ _/_/ "Things are not so easy" _/_/ _/_/ _/_/ _/_/ _/_/ _/_/ "My name is Dump, Core Dump" _/_/_/ _/_/_/ _/_/ _/_/ "El amor es poner tu felicidad en la felicidad de otro" - Leibniz -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQCVAwUBUhG1Q5lgi5GaxT1NAQJ7jgP/TjsodjuTeOTYsUf8gCKC95yeBsgEI6Wi JEANLfwXjxQgaDyD5Mx/v6cmwJU0YJvNu4LwCHOuD+tK7E75XVAw9DIwXiiRQpAO tuMkSb9g78BMVxMxZRhcwKVH+y7DRKK9ADtUPPSBW7FuI9I+TH7vIdD4GpI9VFv/ o55FfgPRUBw= =1CMi -----END PGP SIGNATURE-----

2 1

Timeframe for 2.7.6
by Jesus Cea Aug. 19, 2013

Aug. 19, 2013

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Is there any release date/estimation for 2.7.6?. - -- Jesús Cea Avión _/_/ _/_/_/ _/_/_/ jcea(a)jcea.es - http://www.jcea.es/ _/_/ _/_/ _/_/ _/_/ _/_/ Twitter: @jcea _/_/ _/_/ _/_/_/_/_/ jabber / xmpp:jcea@jabber.org _/_/ _/_/ _/_/ _/_/ _/_/ "Things are not so easy" _/_/ _/_/ _/_/ _/_/ _/_/ _/_/ "My name is Dump, Core Dump" _/_/_/ _/_/_/ _/_/ _/_/ "El amor es poner tu felicidad en la felicidad de otro" - Leibniz -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQCVAwUBUg4/M5lgi5GaxT1NAQIhhQP/YzvPcA9KWNYD8k5S1vNFVi3Qv3STS0UA 1ROP7cD7WIAWalGdRF7TrYVifHFNqfdNR84QYGU6oHGOkGBZMwlUFu9mxbrbsllh GrfmrTQih41xxAqUf1rkqoCmW36YO0TsCw7nNzAIJ0foveEWRPRsti8Z1/0U4Zn6 HWeZF57rCBM= =oRD8 -----END PGP SIGNATURE-----

3 2

PEP commit privilieges for Donald Stufft?
by Nick Coghlan Aug. 14, 2013

Aug. 14, 2013

Donald is the current main developer for PyPI and is doing a lot of work on PyPI related PEPs this days - it would reduce the administrative overhead if he could update the related PEPs directly. Any objections to my getting him to send his public SSH key to hgaccounts for inclusion? Cheers, Nick. -- Nick Coghlan | ncoghlan(a)gmail.com | Brisbane, Australia

6 5

SSH key changed
by Jesus Cea Aug. 14, 2013

Aug. 14, 2013

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I would like to replace my 1024 bit SSH key with a brand new 2048 bit key. What would be the procedure? I am talking about "hg.python.org". I don't think I have any other SSH access under python.org. Please, confirm. Thanks!. - -- Jesús Cea Avión _/_/ _/_/_/ _/_/_/ jcea(a)jcea.es - http://www.jcea.es/ _/_/ _/_/ _/_/ _/_/ _/_/ Twitter: @jcea _/_/ _/_/ _/_/_/_/_/ jabber / xmpp:jcea@jabber.org _/_/ _/_/ _/_/ _/_/ _/_/ "Things are not so easy" _/_/ _/_/ _/_/ _/_/ _/_/ _/_/ "My name is Dump, Core Dump" _/_/_/ _/_/_/ _/_/ _/_/ "El amor es poner tu felicidad en la felicidad de otro" - Leibniz -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQCVAwUBUgpnQJlgi5GaxT1NAQLA9QP+MxaXs4xtdCrtUFVkCAMLzk3pToPQBdTU u0daC0SonpczWhWrKYmTLxuQR5gptzCYV2kdsNCRhw1DtUj5aq/uG7YZyBQ3rpev z/NeAbBsBE3jT7viMzndlJhymR91YBXFz6CTxklDFC7vkVnKUK1W7F/7YYq1r9mv S2u/RVFQMNc= =qNOs -----END PGP SIGNATURE-----

2 2

[RELEASED] Python 3.4.0a1
by Larry Hastings Aug. 4, 2013

Aug. 4, 2013

On behalf of the Python development team, I'm pleased to announce the first alpha release of Python 3.4. This is a preview release, and its use is not recommended for production settings. Python 3.4 includes a range of improvements of the 3.x series, including hundreds of small improvements and bug fixes. Major new features and changes in the 3.4 release series so far include: * PEP 435, a standardized "enum" module * PEP 442, improved semantics for object finalization * PEP 443, adding single-dispatch generic functions to the standard library * PEP 445, a new C API for implementing custom memory allocators To download Python 3.4.0a1 visit: http://www.python.org/download/releases/3.4.0/ Please consider trying Python 3.4.0a1 with your code and reporting any issues you notice to: http://bugs.python.org/ Enjoy! -- Larry Hastings, Release Manager larry at hastings.org (on behalf of the entire python-dev team and 3.4's contributors)

2 3

Trunk is ready for 3.4.0a2 work
by Larry Hastings Aug. 4, 2013

Aug. 4, 2013

All the release engineering work for 3.4.0a1 has been merged. Cry havoc, and let slip the checkins of war! //arry/

2 1

Can I get the keys to the website please?
by Larry Hastings Aug. 4, 2013

Aug. 4, 2013

PEP 101 tells me that in order to release Python 3.4.0a1 I must massage the website. I foolishly left this to the last minute. Can anybody give me access to the repo and shove me towards the README? Pretty please? I already have access to dinsdale and am in the "webmaster" group on there. By the way: unless something explodes last-minute, Python 3.4.0a1 will be based on d86aec3f61b0. Fingers crossed, //arry/

3 2

Tagging 3.4a1 with an unhappy AMD64 Win7 SP1 buildbot?
by Larry Hastings Aug. 3, 2013

Aug. 3, 2013

I'm considering for Python 3.4.0a1. The buildbots are all happy, except for AMD64 Win7 SP1: http://buildbot.python.org/all/waterfall?category=3.x.stable The two failures are zipimport and signal. zipimport is sporadic, and looks like some sort of heisenissue. signal is much more consistently broken, and has been broken for a while. (Not that Windows support for signal has ever been that great. But presumably the regression test is supposed to light up green, even on Windows.) Can we, uh, live with that, for alpha 1? //arry/

4 5

Reminder: Python 3.4 alpha 1 release is Saturday August 3
by Larry Hastings Aug. 3, 2013

Aug. 3, 2013

It's about nine days from now. I expect to tag the release late next week. So if you're doing any major brain surgery, please finish it up in the next week or so. Your mildly anxious release manager, //arry/ p.s. Anybody have contact information for Jim Hugunin? He left Google back in May and has dropped off the face of the internet. I want to interview him for my podcast.

11 18

Re: [python-committers] python-list moderation flag
by Barry Warsaw Aug. 2, 2013

Aug. 2, 2013

On Jul 29, 2013, at 11:25 PM, Brad Knowles wrote: >The postmaster/listmaster folks could potentially act as "emergency backup" >moderators, much like we do for the mailman-* lists, if there was a need for >additional people to help out. However, I suspect this additional work would >need to remain on an "emergency backup" sort of basis. Tim Golden and Terry Reedy have volunteered, so they're both now added. (It's an interesting side discussion about Mailman 3 allowing an ultimate backup for list ownership.) >However, taking off my Postmaster Emeritus hat and speaking only for myself, >after all these years I must confess to you that I'm not actually a Python >programmer, and I do not have the technical qualifications necessary to serve >in the role as one of the primary moderators. No worries! Your help and feedback as always is appreciated. -Barry

1 0