Mailman 3 March 2010 - python-committers

Fwd: [Python-checkins] r78923 - in python/branches/release26-maint: Doc/Makefile Doc/tools/sphinxext/download.html
by Barry Warsaw 15 Mar '10

15 Mar '10

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 <python-checkins(a)python.org> > Date: March 13, 2010 8:42:13 AM EST > To: python-checkins(a)python.org > Subject: [Python-checkins] r78923 - in python/branches/release26-maint: Doc/Makefile Doc/tools/sphinxext/download.html > message-id: <20100313134213.9030CE3C1(a)mail.python.org> > > Author: georg.brandl > Date: Sat Mar 13 14:42:13 2010 > New Revision: 78923 > > Log: > Merged revisions 78921 via svnmerge from > svn+ssh://pythondev@svn.python.org/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 %} > <h1>Download Python {{ release }} Documentation</h1> > > -{% if 'a' in release or 'b' in release or 'c' in release %} > -<p>We don't package the documentation for development releases for download. > - Downloads will be available for the final release.</p> > - > -{% else %} > {% if last_updated %}<p><b>Last updated on: {{ last_updated }}.</b></p>{% endif %} > > <p>To download an archive containing all the documents for this version of > @@ -55,6 +54,4 @@ > > <p>If you have comments or suggestions for the Python documentation, please send > email to <a href="mailto:docs@python.org">docs(a)python.org</a>.</p> > -{% endif %} > - > {% endblock %} > _______________________________________________ > Python-checkins mailing list > Python-checkins(a)python.org > http://mail.python.org/mailman/listinfo/python-checkins

5 8

updating libffi to 3.0.9?
by Matthias Klose 15 Mar '10

15 Mar '10

I would like to update the internal copy of libffi from the 3.0.5 release to 3.0.9 (plus an ARM specific patch checked in after the 3.0.9 release). Is this ok for the trunk and the py3kbranch? I only can check linux targets and watch the buildds, so I would like to ask for tests on other targets. The libffi subdirectories for testsuite, doc and man are currently not checked in. Should these be kept out, or should the complete libffi release be checked in? Thanks, Matthias

4 3

Python 2.6.5 rc 2
by Barry Warsaw 10 Mar '10

10 Mar '10

Hi Python hackateers! It looks like we finally have no more release blockers for 2.6.5rc2. I would like to tag the tree tonight for rc2 so that Martin can build the Windows installer for a release tomorrow. I am also moving the final release back to Friday March 19. -Barry

2 2

release26-maint freeze for 2.6.5rc2 tagging
by Barry Warsaw 09 Mar '10

09 Mar '10

There are currently no showstopper bugs for 2.6.5rc2, so as previously threatened, I am going to tag the release. Please, no commits (even merge blocks) on release26-maint until I do. Ping me on #python-dev if necessary. -Barry

1 0

Python 2.6.5 rc 2
by Barry Warsaw 07 Mar '10

07 Mar '10

We are definitely going to need a 2.6.5 rc 2. We've had a number of critical issues fixed since rc1 and we have two more critical patches approved for landing which fix issues on OS X. I've given Ronald approval in the tracker to land these two patches. 8066 OS X installer: readline module breaks when targeting on 10.5 or 10.6 8067 OS X Installer: build errors on 10.6 when targeting 10.4 and earlier These are the only two release blockers left for 2.6.5 (at the moment). I would like to cut the rc2 release tomorrow, Monday 2010-03-08, so if anybody knows of any other bugs you think must go into 2.6.5, mark them release blockers now so that I can evaluate them. I really don't want there to be an rc3, and I'd still like to get 2.6.5 final out on Monday 2010-03-15. We'll see. -Barry

1 0

branches open
by Benjamin Peterson 06 Mar '10

06 Mar '10

With 3.1.2rc2 and 2.7a4 out, the trunk and the 3.1 branch are open to commits. -- Regards, Benjamin

1 0

doing 2.7a4 and 3.1.2rc1
by Benjamin Peterson 06 Mar '10

06 Mar '10

I'm going to start working on these two releases, so please refrain from making checkins in the trunk or the 3.1 branch. Thanks! -- Regards, Benjamin

1 0

SSH keys and Keychain
by Vinay Sajip 04 Mar '10

04 Mar '10

I'm having some odd problems with my SSH key and Keychain which I hope someone on this list can help with. When I became a Python committer, I was using Windows, mostly, so I set up an SSH key using PuTTY and Pageant which worked flawlessly. More recently, I've being using Linux, mostly, as my primary development environment, so I copied the key over from my Windows boxes. I can get access, but I keep on getting repeatedly prompted for the passphrase. I've installed Keychain and invoked it in my .bashrc, and whenever I open a terminal session, it tells me that it found an existing ssh-agent and the SSH_AUTH_SOCK and SSH_AGENT_PID seem to be correct. Yet, I get prompted for the passphrase for every SVN operation. If I invoke ssh-add -L to see what keys have been added, the original SSH key I copied over is there (there are two SSH keys, not that this should cause problems: ~/.ssh/id_rsa holds the key I copied over from Windows, and another more recent key I generated on my Linux host, which I've stored as ~/.ssh/id_rsa_jaunty). Anyone know what might be causing this? Thanks for any help, Vinay Sajip

7 13

Unapproved commits after 2.6.5rc1
by Barry Warsaw 03 Mar '10

03 Mar '10

There have been a couple of commits to the Python 2.6 branch since the 2.6.5rc1 tag. Since these were done by Florent and Victor, I just wanted to re-iterate that all substantive changes (i.e. anything other than svnmerge blocks) need to be approved while we're in release candidate mode. To get a change in between rc's and final releases, you should: * Create or elevate a bug to be a release blocker * Attach your patch to the bug * Discuss the change here or on python-dev * Get approval for the change by me either via IRC or email The revisions in question are Victor's r78597 and Florent's r78621. Since these are not critical fixes, I am going to revert them. -Barry

9 15

2.6.5
by Barry Warsaw 01 Mar '10

01 Mar '10

The tarballs for Python 2.6.5 rc1 have been uploaded, the branch tagged, and the website fiddled. I want to semi-unfreeze the release26-maint branch. Since this was a release candidate, only patches fixing release blockers, or other brown paper bag bugs will be allowed. Contact me via email, bug tracker or IRC if you want to get something in. Please do download and test the release candidate with your favorite software. I won't announce it to the wider community until Martin has uploaded the Windows installer. Your testing will help make 2.6.5 final a great, solid release! http://www.python.org/download/releases/2.6.5/ Cheers, -Barry

1 0