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 do
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
Am 06.09.2013 13:06, schrieb Larry Hastings:
It's been pretty quiet, and there aren't any genuine release blockers
(everything marked release blocker and 3.4 is actually for 2.6.9). I
expect to tag Saturday evening, New Zealand time.
IMO, http://bugs.python.org/issue18852 should be made a rel
Matthias Klose schrieb:
> 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 woul
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", "cop
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
I'd like to request review (or whatever is needed to get permission
to fix this bug and commit the patch into trunk, py3k and release25-maint).
http://bugs.python.org/issue3547
--
Thanks,
Thomas
___
python-committers mailing list
python-committers@pyt
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 revi
