Re: [python-committers] [RELEASE] Python 3.4.2rc1 is now available

2014-09-23 Thread Thomas Heller
Am 23.09.2014 um 01:10 schrieb Terry Reedy: On 9/22/2014 2:12 PM, Ned Deily wrote: This page still has this misleading section and sentence Download Please proceed to the download page for the download. but it now links to itself rather than the 341 page. This should be removed. The actual

Re: [python-committers] Reminder: 3.4a2 to be tagged soon

2013-09-06 Thread Thomas Heller
Am 06.09.2013 15:24, schrieb Thomas Heller: IMO, http://bugs.python.org/issue18852 should be made a release blocker; it requires me to either uninstall pyreadline or patch site.py otherwise there are errors starting python 3.4. Thanks to anyone involved for fixing this. Thomas

Re: [python-committers] Python 2.6.4?

2009-10-04 Thread Thomas Heller
Martin v. Löwis schrieb: It seems logging is broken in 2.6.3. Should we release 2.6.4 quickly? http://bugs.python.org/issue7052 It also reports a 2.6.3rc1 version number on windows: Python 2.6.3 (r263rc1:75186, Oct 2 2009, 20:40:30) [MSC v.1500 32 bit (Intel)] on win32 Type help,

Re: [python-committers] Survey about DVCSs compared to svn

2009-02-28 Thread Thomas Heller
Brett Cannon schrieb: I had a long reply all written out, but instead I decided to discard it so as to not continue to drag this discussion out. Why? The DVCS PEP is not even finished yet! Can you guys please let me finish the PEP before you start worrying about whether we are going to

Re: [python-committers] PQM?

2008-08-14 Thread Thomas Heller
Christian Heimes schrieb: I suggest that we should use branches to a greater extend. New features or updates of existing code should happen on a branch. +1 A branch must not be merged until it's tested on all major platforms (Linux i386, Linux AMD64, Mac OS X and Win32) and peer reviewed