Robert Brewer writes:
> Python 3.1 was released June 27th, 2009. We're coming up faster on the
> two-year period than we seem to be on a revised WSGI spec. Maybe we
> should shoot for a "bytes of a known encoding" type first.
You have one. It's called "ISO 2022: Information processing -- ISO
Antoine Pitrou wrote:
> > I can reproduce this with release27-maint on Fedora-14/amd64/gcc-4.6.
> > -fno-strict-aliasing is enabled.
>
> It might be interesting to have a buildbot with a bleeding edge
> toolchain. Although in this case nobody rushed to diagnose the
> three-month old issue anyway:
On Sat, 8 Jan 2011 22:58:51 +0100
Stefan Krah wrote:
> Antoine Pitrou wrote:
> > On Sat, 8 Jan 2011 12:03:35 -0800 (PST)
> > "Ralf W. Grosse-Kunstleve" wrote:
> > > I just wanted to share an observation in case Python developers are
> > > interested:
> > > Python 2.7.1 doesn't build with the cur
On Sat, 08 Jan 2011 23:05:06 +0100
brett.cannon wrote:
> +For bugs, an issue needs to:
> +
> +* Clearly explain the bug so it can be reproduced
> +* All relevant platform details are included
> +* What version(s) of Python are affected by the bug are fully known
> +* Is there a proper unit test th
Antoine Pitrou wrote:
> On Sat, 8 Jan 2011 12:03:35 -0800 (PST)
> "Ralf W. Grosse-Kunstleve" wrote:
> > I just wanted to share an observation in case Python developers are
> > interested:
> > Python 2.7.1 doesn't build with the current gcc 4.6 svn.
> > Note that gcc 4.6 is now in "bug-fix only" m
> BTW: I've been doing gcc pre-release testing regularly for many year,
> starting
> with gcc 3.3. This is the first time I see the Python build fail persistently
> for several weeks.
Wild guess: did configure detect that it needs to use -fno-strict-aliasing?
Regards,
Martin
__
On Sat, 8 Jan 2011 12:03:35 -0800 (PST)
"Ralf W. Grosse-Kunstleve" wrote:
> I just wanted to share an observation in case Python developers are
> interested:
> Python 2.7.1 doesn't build with the current gcc 4.6 svn.
> Note that gcc 4.6 is now in "bug-fix only" mode.
You should report a bug with
In article
,
Brett Cannon wrote:
> On Thu, Jan 6, 2011 at 13:04, Ned Deily wrote:
> > In article ,
> > brett.cannon wrote:
> > [...]
> >> summary:
> >> Point out that OS X users need to change examples to use python.exe
> >> instead
> >> of python.
> >> Once Python is done building you
On Thu, Jan 6, 2011 at 13:04, Ned Deily wrote:
> In article ,
> brett.cannon wrote:
> [...]
>> summary:
>> Point out that OS X users need to change examples to use python.exe instead
>> of python.
>> Once Python is done building you will then have a working build of Python
>> that can be r
'-DNDEBUG -g -fwrapv -O3 -Wall
-Wstrict-prototypes' ./python -E ./setup.py build
make: *** [sharedmods] Error 139
g++ (GCC) 4.6.0 20110108 (experimental)
% make
XXX lineno: 743, opcode: 0
Traceback (most recent call last):
File "/net/theta/raid1/rwgk/junk/Python-2.7.1/Lib/site.py"
On Sat, 8 Jan 2011 04:16:05 +0100 (CET)
victor.stinner wrote:
> Author: victor.stinner
> Date: Sat Jan 8 04:16:05 2011
> New Revision: 87849
>
> Log:
> test_ssl: test SHA256 using sha256.tbs-internet.com instead of sha2.hboeck.de
>
> Modified:
>python/branches/py3k/Lib/test/test_ssl.py
>
11 matches
Mail list logo