Mailman 3 November 2010 - python-committers

Deny nonbreaking spaces in the precommit script?
by Victor Stinner 09 Nov '10

09 Nov '10

Hi, I introduced nonbreaking spaces in Lib/os.py in a comment, because I kept Alt Gr. key pressed to write the space after # (stupid Xorg keyboard variant!). This change introduces a strange bug in "LANG=C ./python -m test.regrtest -v test_imp test_trace" command. The real bug was fixed in issue #10329, but I would like to know if it would be possible to block a commit introducing nonbreaking spaces? A least for me :-) Victor

13 27

Need help with read-write checkouts (Win/TortoiseSVN)
by Terry Reedy 09 Nov '10

09 Nov '10

Wanting to finish up the difflib issue (#2986) with my first commits, I read http://www.python.org/dev/faq/ (especially 2.2.2 and 2.3), loaded TortoiseSVN, and successfully did a read-only checkout. But when I try to do the needed read-write checkout, I get a blank plink screen and ... nothing. I tried both with 'pythondev@' and Pageant running and without both after creating a svn.python.org profile. And ideas what to do next? Is there some step missing from the faq? In attempting to verify that my commit privileges are working (2.8.2), I noticed that in order to log in with putty, or 'register' the private key with pageant, I need a 'passphrase'. If I gave one when generating the key, I have no memory of it and cannot find such written down after extensive search. So if either of the above is the unmentioned missing step, I will need for someone to replace my current public key after I generate a new pair. Who is currently available to do so? For once, I would like copies of helpful responses sent directly to me. I am signed up for the digest version of this list and cannot login to change that. Mailman will not (at the moment, at least) accept the password that it generated for me and that it sends in the monthly reminders. -- Terry Jan Reedy

3 4

New schedule for 3.2
by Georg Brandl 08 Nov '10

08 Nov '10

Hi, on a request by Martin, I added another alpha to the Python 3.2 release schedule. The scheduled releases are now - 3.2 alpha 4: November 13, 2010 - 3.2 beta 1: December 4, 2010 - 3.2 beta 2: December 18, 2010 - 3.2 candidate 1: January 8, 2010 - 3.2 candidate 2: January 22, 2011 - 3.2 final: February 5, 2011 So you have three weeks more to add your favorite new features to 3.2 -- use them wisely! 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.

2 1