Mailman 3 - python-committers

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

Fw: [Python-checkins] r78573 - python/tags/r265rc1
by Barry Warsaw 01 Mar '10

01 Mar '10

Hi Martin and Ronald, We are tagged for 2.6.5 rc 1. Please let me know when the installers are uploaded. -Barry

1 0

Python 2.6.5 rc 1
by Barry Warsaw 01 Mar '10

01 Mar '10

Remember, I am cutting the 2.6.5 rc 1 release today, probably in about 90 minutes. I have a patch to commit for bug 7250, which unfortunately doesn't appear to be unit-testable. :( I'm hoping someone will be able to test this in a live environment. Please refrain from committing anything to the release26-maint branch without pinging me first on #python-dev. I'll send another message after the thaw. -Barry

1 0

Python 2.6.5 rc 1
by Barry Warsaw 26 Feb '10

26 Feb '10

Hello everybody! I hope you all had as great a time at Pycon 2010 as I did. No time to begin recovering though, we're on to Python 2.6.5 rc 1, which I would like to release on Monday. We have one showstopper still open, and I'll try to respond to that asap. http://bugs.python.org/issue7250 If there is anything else that absolutely should go into 2.6.5, now's the time to let me know. If there are no patches ready to be reviewed and landed though, you're probably running out of time. I will be very conservative about landing patches after rc1. Cheers, -Barry

1 0

Commit access for David Malcolm
by Jeffrey Yasskin 21 Feb '10

21 Feb '10

Hi all, David Malcolm is the Fedora maintainer for the Python package and has written a gdb plugin to replace and dramatically improve our old Misc/gdbinit file using the new python scripting support in gdb-7. You can see it in action at http://fedoraproject.org/wiki/Features/EasierPythonDebugging#User_Experience. I'd like to get this into our repository asap, but he's also going to be improving it fairly quickly. So it'd be nice if he could commit his improvements directly. Do you guys think we should give him commit access so he can make gdb and packaging-related changes? Jeffrey

8 8

trunk open
by Benjamin Peterson 06 Feb '10

06 Feb '10

2.7a3 is out, so feel free to commit again. -- Regards, Benjamin

1 0

2.7 alpha 3
by Benjamin Peterson 06 Feb '10

06 Feb '10

Please no checkins to the trunk while I do the release. -- Regards, Benjamin

1 0

trunk open
by Benjamin Peterson 09 Jan '10

09 Jan '10

With 2.7a2 out, the trunk is now available for development towards 2.7 alpha 3. -- Regards, Benjamin

1 0