[python-committers] Fwd: [Python-checkins] r78923 - in python/branches/release26-maint: Doc/Makefile Doc/tools/sphinxext/download.html
I'm not necessarily saying these shouldn't go into 2.6.5, but this late in the release cycle, every change needs to be justified. My preferred way of doing so is by filing a release blocker issue stating and backing up the requested change. We can then discuss any potential impact on release testing and schedule. I'm fine with one issue if all these commits to the release26-maint branch are for the same issue. Georg, please file that bug so we can formally decide whether or not to include these in 2.6.5 final, and whether or not they require a 2.6.5 rc 3 (which as you know I really don't want to do! ;) Thanks, -Barry Begin forwarded message: > From: georg.brandl > Date: March 13, 2010 8:42:13 AM EST > To: [email protected] > Subject: [Python-checkins] r78923 - in python/branches/release26-maint: > Doc/Makefile Doc/tools/sphinxext/download.html > message-id: <[email protected]> > > Author: georg.brandl > Date: Sat Mar 13 14:42:13 2010 > New Revision: 78923 > > Log: > Merged revisions 78921 via svnmerge from > svn+ssh://[email protected]/python/trunk > > > r78921 | georg.brandl | 2010-03-13 14:39:46 +0100 (Sa, 13 Mär 2010) | 1 line > > Change/fix handling of docs download location: for daily builds, put them > right next to the HTML. > > > > Modified: > python/branches/release26-maint/ (props changed) > python/branches/release26-maint/Doc/Makefile > python/branches/release26-maint/Doc/tools/sphinxext/download.html > > Modified: python/branches/release26-maint/Doc/Makefile > == > --- python/branches/release26-maint/Doc/Makefile (original) > +++ python/branches/release26-maint/Doc/Makefile Sat Mar 13 14:42:13 2010 > @@ -157,16 +157,17 @@ > check: > $(PYTHON) tools/rstlint.py -i tools > > -# Targets for automatic doc build > +# Targets for daily automated doc build > > # for development releases: always build > autobuild-dev: > make update > - make dist > + make dist SPHINXOPTS='-A daily=1' > > -# for stable releases: only build if not in development mode > +# for stable releases: only build if not in pre-release stage (alpha, beta, > rc) > autobuild-stable: > @case $(DISTVERSION) in *[abc]*) \ > - echo "Not building; not a release version."; exit 1;; \ > + echo "Not building; $(DISTVERSION) is not a release version."; \ > + exit 1;; \ > esac > @make autobuild-dev > > Modified: python/branches/release26-maint/Doc/tools/sphinxext/download.html > == > --- python/branches/release26-maint/Doc/tools/sphinxext/download.html > (original) > +++ python/branches/release26-maint/Doc/tools/sphinxext/download.html Sat Mar > 13 14:42:13 2010 > @@ -1,15 +1,14 @@ > {% extends "layout.html" %} > {% set title = 'Download' %} > -{% set dlbase = 'http://docs.python.org/ftp/python/doc/current' %} > -{% block body %} > +{% if daily is defined %} > + {% set dlbase = pathto('archives', 1) %} > +{% else %} > + {% set dlbase = 'http://docs.python.org/ftp/python/doc/' + release %} > +{% endif %} > > +{% block body %} > Download Python {{ release }} Documentation > > -{% if 'a' in release or 'b' in release or 'c' in release %} > -We don't package the documentation for development releases for download. > - Downloads will be available for the final release. > - > -{% else %} > {% if last_updated %}Last updated on: {{ last_updated }}.{% > endif %} > > To download an archive containing all the documents for this version of > @@ -55,6 +54,4 @@ > > If you have comments or suggestions for the Python documentation, please > send > email to mailto:[email protected]";>[email protected]. > -{% endif %} > - > {% endblock %} > ___ > Python-checkins mailing list > [email protected] > http://mail.python.org/mailman/listinfo/python-checkins ___ python-committers mailing list [email protected] http://mail.python.org/mailman/listinfo/python-committers
Re: [python-committers] Fwd: [Python-checkins] r78923 - in python/branches/release26-maint: Doc/Makefile Doc/tools/sphinxext/download.html
Am 13.03.2010 17:51, schrieb Barry Warsaw: > I'm not necessarily saying these shouldn't go into 2.6.5, but this late in > the release cycle, every change needs to be justified. My preferred way of > doing so is by filing a release blocker issue stating and backing up the > requested change. We can then discuss any potential impact on release > testing and schedule. I'm fine with one issue if all these commits to the > release26-maint branch are for the same issue. > Georg, please file that bug so we can formally decide whether or not to > include these in 2.6.5 final, and whether or not they require a 2.6.5 rc 3 > (which as you know I really don't want to do! ;) No need to file a new issue -- I've promoted 8111 to release blocker. I've added an explanation and a collective diff. No further RC is needed. Sorry for directly committing this, but I felt it was within my disgression as Documentation Expert and just fair -- after all PEP 101 states you have to get my approval during the release process, which I didn't see for these RCs :) cheers, Georg -- Thus spake the Lord: Thou shalt indent with four spaces. No more, no less. Four shall be the number of spaces thou shalt indent, and the number of thy indenting shall be four. Eight shalt thou not indent, nor either indent thou two, excepting that thou then proceed to four. Tabs are right out. ___ python-committers mailing list [email protected] http://mail.python.org/mailman/listinfo/python-committers
Re: [python-committers] Fw: [Python-checkins] r78823 - python/tags/r265rc2
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03/10/2010 05:42 PM, Barry Warsaw wrote: > All: The release26-maint branch is now semi-thawed. I'm going to be even more > strict about commits to the branch now because I really don't want to release > an rc3 unless absolutely necessary. 2.6.5 final is scheduled for 2010-03-19. I was wondering about http://bugs.python.org/issue3928 . It is a trivial fix a couple of lines long only. - -- Jesus Cea Avion _/_/ _/_/_/_/_/_/ [email protected] - http://www.jcea.es/ _/_/_/_/ _/_/_/_/ _/_/ jabber / xmpp:[email protected] _/_/_/_/ _/_/_/_/_/ . _/_/ _/_/_/_/ _/_/ _/_/ "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.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQCVAwUBS5vqqZlgi5GaxT1NAQKRAAP/WPud1hZkfkFvTvbbC7W/GciTABJmPlRZ 5daUYn/kafC4lJ+ZaVM7cp1wX5xj6ZxVmVLzG3xwvtJR5o1kS3UAsLbM9fwUkHFb j7myKQRpw2GanheidsSP0Tfms8emW+UVnxUH8jYK5m8jnIdauVYp+MkEWJOk2Lwi xZYGH+jKels= =SqKW -END PGP SIGNATURE- ___ python-committers mailing list [email protected] http://mail.python.org/mailman/listinfo/python-committers
Re: [python-committers] Fw: [Python-checkins] r78823 - python/tags/r265rc2
Le Sat, 13 Mar 2010 20:42:33 +0100, Jesus Cea a écrit : > > I was wondering about http://bugs.python.org/issue3928 . It is a > trivial fix a couple of lines long only. We have lots of "trivial" fixes in the tracker, though. ___ python-committers mailing list [email protected] http://mail.python.org/mailman/listinfo/python-committers
Re: [python-committers] Fw: [Python-checkins] r78823 - python/tags/r265rc2
Antoine Pitrou wrote: > Le Sat, 13 Mar 2010 20:42:33 +0100, > Jesus Cea a écrit : >> I was wondering about http://bugs.python.org/issue3928 . It is a >> trivial fix a couple of lines long only. > > We have lots of "trivial" fixes in the tracker, though. It's not a regression from 2.6.4, so it's clearly out of scope for 2.6.5, IMO. Regards, Martin ___ python-committers mailing list [email protected] http://mail.python.org/mailman/listinfo/python-committers
Re: [python-committers] Fw: [Python-checkins] r78823 - python/tags/r265rc2
On Mar 13, 2010, at 08:42 PM, Jesus Cea wrote: >I was wondering about http://bugs.python.org/issue3928 . It is a trivial >fix a couple of lines long only. These can be addressed for 2.6.6. -Barry signature.asc Description: PGP signature ___ python-committers mailing list [email protected] http://mail.python.org/mailman/listinfo/python-committers
Re: [python-committers] Fwd: [Python-checkins] r78923 - in python/branches/release26-maint: Doc/Makefile Doc/tools/sphinxext/download.html
On Mar 13, 2010, at 07:11 PM, Georg Brandl wrote: >No need to file a new issue -- I've promoted 8111 to release blocker. >I've added an explanation and a collective diff. No further RC is needed. Thanks; I've accepted and closed the issue. >Sorry for directly committing this, but I felt it was within my disgression >as Documentation Expert and just fair -- after all PEP 101 states you have >to get my approval during the release process, which I didn't see for >these RCs :) This is true. :) I really appreciate the fix, and you're definitely right that it's your discretion to make these commits. I'm just being overly paranoid during rc2->final because I'm really hoping to avoid an rc3. For me, your bug report was perfect because it explained what and why you were doing it, and that you're confident an rc3 isn't needed. But I want to make sure that you're cool with the process, so let me know if you think I went too far. -Barry signature.asc Description: PGP signature ___ python-committers mailing list [email protected] http://mail.python.org/mailman/listinfo/python-committers
[python-committers] Is 3.1 open? (was: Re: Fw: [Python-checkins] r78823 - python/tags/r265rc2)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03/13/2010 11:25 PM, Barry Warsaw wrote: > On Mar 13, 2010, at 08:42 PM, Jesus Cea wrote: > >> I was wondering about http://bugs.python.org/issue3928 . It is a trivial >> fix a couple of lines long only. > > These can be addressed for 2.6.6. Your word is my command, Barry. What about 3.1.3, Benjamin?. I guess it is too late for 3.1.2, since the rc is out. I saw your message asking for stopping commits the 6th march, but I haven't seen another message opening the gates again... - -- Jesus Cea Avion _/_/ _/_/_/_/_/_/ [email protected] - http://www.jcea.es/ _/_/_/_/ _/_/_/_/ _/_/ jabber / xmpp:[email protected] _/_/_/_/ _/_/_/_/_/ . _/_/ _/_/_/_/ _/_/ _/_/ "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.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQCVAwUBS5wbYJlgi5GaxT1NAQLw+QP/e2cK8aWOqsU7Yt1/HepqujOzlptdeZ7h mBmm20aWWQ5+frgO6+y8SbV2bKxSGdFt2KRhk1WwHIkZFTXDBEYs/iBpQB/Cfp80 bRxBjrvN3X5dLDQ5DJd6TDvKbypqTPGT8uJoZYDf+Gws9aKp4IRKi7btZAOA5I8G Gi1xfR4IqsE= =rAib -END PGP SIGNATURE- ___ python-committers mailing list [email protected] http://mail.python.org/mailman/listinfo/python-committers
Re: [python-committers] Is 3.1 open? (was: Re: Fw: [Python-checkins] r78823 - python/tags/r265rc2)
2010/3/13 Jesus Cea : > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On 03/13/2010 11:25 PM, Barry Warsaw wrote: >> On Mar 13, 2010, at 08:42 PM, Jesus Cea wrote: >> >>> I was wondering about http://bugs.python.org/issue3928 . It is a trivial >>> fix a couple of lines long only. >> >> These can be addressed for 2.6.6. > > Your word is my command, Barry. > > What about 3.1.3, Benjamin?. I guess it is too late for 3.1.2, since the > rc is out. I saw your message asking for stopping commits the 6th march, > but I haven't seen another message opening the gates again... As Martin pointed out, I don't think this patch is acceptable for a bug fix release. -- Regards, Benjamin ___ python-committers mailing list [email protected] http://mail.python.org/mailman/listinfo/python-committers
Re: [python-committers] Is 3.1 open? (was: Re: Fw: [Python-checkins] r78823 - python/tags/r265rc2)
Le Sat, 13 Mar 2010 17:19:39 -0600, Benjamin Peterson a écrit : > > > > What about 3.1.3, Benjamin?. I guess it is too late for 3.1.2, > > since the rc is out. I saw your message asking for stopping commits > > the 6th march, but I haven't seen another message opening the gates > > again... > > As Martin pointed out, I don't think this patch is acceptable for a > bug fix release. I would say the patch is acceptable for a bugfix release, just not one in release candidate status. Regards Antoine. ___ python-committers mailing list [email protected] http://mail.python.org/mailman/listinfo/python-committers
Re: [python-committers] Fwd: [Python-checkins] r78923 - in python/branches/release26-maint: Doc/Makefile Doc/tools/sphinxext/download.html
Am 14.03.2010 00:08, schrieb Barry Warsaw: > On Mar 13, 2010, at 07:11 PM, Georg Brandl wrote: > >>No need to file a new issue -- I've promoted 8111 to release blocker. >>I've added an explanation and a collective diff. No further RC is needed. > > Thanks; I've accepted and closed the issue. > >>Sorry for directly committing this, but I felt it was within my disgression >>as Documentation Expert and just fair -- after all PEP 101 states you have >>to get my approval during the release process, which I didn't see for >>these RCs :) > > This is true. :) I really appreciate the fix, and you're definitely right > that it's your discretion to make these commits. I'm just being overly > paranoid during rc2->final because I'm really hoping to avoid an rc3. For me, > your bug report was perfect because it explained what and why you were doing > it, and that you're confident an rc3 isn't needed. But I want to make sure > that you're cool with the process, so let me know if you think I went too far. No, I don't -- I quite understand that you want to know what's going on in "your" branch so close to the final, and I should have known that. I'll be in the same position soon for 3.2. So, thanks for bringing it up. cheers, Georg -- Thus spake the Lord: Thou shalt indent with four spaces. No more, no less. Four shall be the number of spaces thou shalt indent, and the number of thy indenting shall be four. Eight shalt thou not indent, nor either indent thou two, excepting that thou then proceed to four. Tabs are right out. ___ python-committers mailing list [email protected] http://mail.python.org/mailman/listinfo/python-committers
Re: [python-committers] Is 3.1 open?
>>> What about 3.1.3, Benjamin?. I guess it is too late for 3.1.2, >>> since the rc is out. I saw your message asking for stopping commits >>> the 6th march, but I haven't seen another message opening the gates >>> again... >> As Martin pointed out, I don't think this patch is acceptable for a >> bug fix release. > > I would say the patch is acceptable for a bugfix release, just not one > in release candidate status. That's what I meant as well. Martin ___ python-committers mailing list [email protected] http://mail.python.org/mailman/listinfo/python-committers
Re: [python-committers] Is 3.1 open?
2010/3/13 "Martin v. Löwis" : What about 3.1.3, Benjamin?. I guess it is too late for 3.1.2, since the rc is out. I saw your message asking for stopping commits the 6th march, but I haven't seen another message opening the gates again... >>> As Martin pointed out, I don't think this patch is acceptable for a >>> bug fix release. >> >> I would say the patch is acceptable for a bugfix release, just not one >> in release candidate status. > > That's what I meant as well. Very well then, let's wait for 3.1.3. -- Regards, Benjamin ___ python-committers mailing list [email protected] http://mail.python.org/mailman/listinfo/python-committers
[python-committers] Frozen branches in Hg
Am 14.03.2010 00:35, schrieb Georg Brandl: > Am 14.03.2010 00:08, schrieb Barry Warsaw: >> On Mar 13, 2010, at 07:11 PM, Georg Brandl wrote: >> >>>No need to file a new issue -- I've promoted 8111 to release blocker. >>>I've added an explanation and a collective diff. No further RC is needed. >> >> Thanks; I've accepted and closed the issue. >> >>>Sorry for directly committing this, but I felt it was within my disgression >>>as Documentation Expert and just fair -- after all PEP 101 states you have >>>to get my approval during the release process, which I didn't see for >>>these RCs :) >> >> This is true. :) I really appreciate the fix, and you're definitely right >> that it's your discretion to make these commits. I'm just being overly >> paranoid during rc2->final because I'm really hoping to avoid an rc3. For >> me, >> your bug report was perfect because it explained what and why you were doing >> it, and that you're confident an rc3 isn't needed. But I want to make sure >> that you're cool with the process, so let me know if you think I went too >> far. > > No, I don't -- I quite understand that you want to know what's going on in > "your" branch so close to the final, and I should have known that. I'll be > in the same position soon for 3.2. So, thanks for bringing it up. Thinking of that a bit more: after the Hg transition, shouldn't we be able to really freeze a branch that is in pre-release approval-needed mode? It is trivial for anyone to commit a fix to their own branch, and then instead of pushing they'd have to notify the release manager to pull from them, as the only person who can push to the frozen branch. Dirkjan, is that feasible? Georg -- Thus spake the Lord: Thou shalt indent with four spaces. No more, no less. Four shall be the number of spaces thou shalt indent, and the number of thy indenting shall be four. Eight shalt thou not indent, nor either indent thou two, excepting that thou then proceed to four. Tabs are right out. ___ python-committers mailing list [email protected] http://mail.python.org/mailman/listinfo/python-committers
Re: [python-committers] Frozen branches in Hg
> Thinking of that a bit more: after the Hg transition, shouldn't we be able to > really freeze a branch that is in pre-release approval-needed mode? It is > trivial for anyone to commit a fix to their own branch, and then instead of > pushing they'd have to notify the release manager to pull from them, as the > only person who can push to the frozen branch. FWIW, it would be possible to freeze a branch also in subversion, today. As for pulling from committer branches: that would require that committers host their branches somewhere. Regards, Martin ___ python-committers mailing list [email protected] http://mail.python.org/mailman/listinfo/python-committers
Re: [python-committers] Frozen branches in Hg
Am 14.03.2010 00:53, schrieb "Martin v. Löwis": >> Thinking of that a bit more: after the Hg transition, shouldn't we be able to >> really freeze a branch that is in pre-release approval-needed mode? It is >> trivial for anyone to commit a fix to their own branch, and then instead of >> pushing they'd have to notify the release manager to pull from them, as the >> only person who can push to the frozen branch. > > FWIW, it would be possible to freeze a branch also in subversion, today. Yes, but I'm sure we don't want to bother setting that up so close to the switch :) > As for pulling from committer branches: that would require that > committers host their branches somewhere. Yes. But that's no big deal, isn't it? They can use a public hg hoster like bitbucket, or we can have a facility on hg.python.org -- it doesn't really matter where, it is always very easy to publish a hg branch. Georg -- Thus spake the Lord: Thou shalt indent with four spaces. No more, no less. Four shall be the number of spaces thou shalt indent, and the number of thy indenting shall be four. Eight shalt thou not indent, nor either indent thou two, excepting that thou then proceed to four. Tabs are right out. ___ python-committers mailing list [email protected] http://mail.python.org/mailman/listinfo/python-committers
Re: [python-committers] Frozen branches in Hg
Le Sun, 14 Mar 2010 01:03:00 +0100, Georg Brandl a écrit : > > > As for pulling from committer branches: that would require that > > committers host their branches somewhere. > > Yes. But that's no big deal, isn't it? They can use a public hg > hoster like bitbucket, or we can have a facility on hg.python.org -- > it doesn't really matter where, it is always very easy to publish a > hg branch. Or people can just use "hg out" or "hg export". ___ python-committers mailing list [email protected] http://mail.python.org/mailman/listinfo/python-committers
Re: [python-committers] Is 3.1 open?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03/14/2010 12:40 AM, Benjamin Peterson wrote: > 2010/3/13 "Martin v. Löwis" : > What about 3.1.3, Benjamin?. I guess it is too late for 3.1.2, > since the rc is out. I saw your message asking for stopping commits > the 6th march, but I haven't seen another message opening the gates > again... As Martin pointed out, I don't think this patch is acceptable for a bug fix release. >>> >>> I would say the patch is acceptable for a bugfix release, just not one >>> in release candidate status. >> >> That's what I meant as well. > > Very well then, let's wait for 3.1.3. That was what I was asking. I will commit the patch to trunk and py3k, and to 2.6 and 3.1 branch after 2.6.5 and 3.1.2 are out. Should I commit now to trunk/py3k and later to 2.6/3.1, or wait to do the four commits at the same time?. Don't want to miss the 2.7beta. Mercurial, where are you?. This would be a non issue :) - -- Jesus Cea Avion _/_/ _/_/_/_/_/_/ [email protected] - http://www.jcea.es/ _/_/_/_/ _/_/_/_/ _/_/ jabber / xmpp:[email protected] _/_/_/_/ _/_/_/_/_/ . _/_/ _/_/_/_/ _/_/ _/_/ "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.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQCVAwUBS5xGeJlgi5GaxT1NAQK24AP+P2w6+11IHzPg9aJk0mmTjonWTBN3Yyqe o209qKwtKGY5VCs90ttoo/3HyUKWk7T45qjXJ+3yQzLkLmIe0YFkacPQ1zo1RtWS 4mdzp/3uSktpq6/b9ejrmYhyqQzSAqCZJHkMPwaycTfjEUoxwH4V+2E+6zx8zZ58 E9W4vy1zc3k= =YDlC -END PGP SIGNATURE- ___ python-committers mailing list [email protected] http://mail.python.org/mailman/listinfo/python-committers
Re: [python-committers] Is 3.1 open?
2010/3/13 Jesus Cea : > I will commit the patch to trunk and py3k, and to 2.6 and 3.1 branch > after 2.6.5 and 3.1.2 are out. > > Should I commit now to trunk/py3k and later to 2.6/3.1, or wait to do > the four commits at the same time?. Don't want to miss the 2.7beta. That's up to you. > > Mercurial, where are you?. This would be a non issue :) How so? -- Regards, Benjamin ___ python-committers mailing list [email protected] http://mail.python.org/mailman/listinfo/python-committers
Re: [python-committers] Is 3.1 open?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03/14/2010 03:35 AM, Benjamin Peterson wrote: >> Mercurial, where are you?. This would be a non issue :) > > How so? The release manager could clone the repository to getting it ready for release, while the main repository accepts new changesets. The point would be not stopping commits, ever. When done, the release manager could tag the release in his/her clone and push the changes to the main branch, like any other commit. If the release manager needs some patches for the main repository, he/she can cherrypick them manually or using a tool like http://mercurial.selenic.com/wiki/TransplantExtension . The devil is in the details, like how the release manager repository clone accesses buildbots, for instance. This is possible workflow. I don't know what is the actual plan, yet. - -- Jesus Cea Avion _/_/ _/_/_/_/_/_/ [email protected] - http://www.jcea.es/ _/_/_/_/ _/_/_/_/ _/_/ jabber / xmpp:[email protected] _/_/_/_/ _/_/_/_/_/ . _/_/ _/_/_/_/ _/_/ _/_/ "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.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQCVAwUBS5xPUZlgi5GaxT1NAQJ6zgP+MOYKeZqMnSHZYATJ2TFMb1mRW1IjjSg6 kdlpLwaLIEM6QKjs6gAJP4QNmIigH0l7gJlZkDaP+FpD90teAbGqJe5xNKyQeZLg xitTu2spFZu8pD2GSZ1GLSq917poOyntYsyLhZ/ICS1QiUPiQItvUIhP3AEociEy WxzRJIZmrMg= =HmlY -END PGP SIGNATURE- ___ python-committers mailing list [email protected] http://mail.python.org/mailman/listinfo/python-committers
