Re: [Python-Dev] r87849 - python/branches/py3k/Lib/test/test_ssl.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
>
> Modified: python/branches/py3k/Lib/test/test_ssl.py
> ==
> --- python/branches/py3k/Lib/test/test_ssl.py (original)
> +++ python/branches/py3k/Lib/test/test_ssl.py Sat Jan 8 04:16:05 2011
> @@ -599,8 +599,8 @@
> # SHA256 was added in OpenSSL 0.9.8
> if ssl.OPENSSL_VERSION_INFO < (0, 9, 8, 0, 15):
> self.skipTest("SHA256 not available on %r" % ssl.OPENSSL_VERSION)
> -# NOTE: https://sha256.tbs-internet.com is another possible test host
> -remote = ("sha2.hboeck.de", 443)
> +# https://sha2.hboeck.de/ was used until 2011-01-08 (no route to
> host)
> +remote = ("sha256.tbs-internet.com", 443)
> sha256_cert = os.path.join(os.path.dirname(__file__), "sha256.pem")
> with support.transient_internet("sha2.hboeck.de"):
You obviously need to update the certificate file and also the host
name above.
___
Python-Dev mailing list
[email protected]
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
[Python-Dev] FYI: Python 2.7.1 + gcc 4.6 (experimental) probable optimizer problem
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. Some details: Fedora 14 64-bit. The first time I noticed the problem was in Nov or early Dec 2010; I'm pretty sure it worked in Oct maybe still early Nov. Python configured simply with ./configure g++ (GCC) 4.6.0 20101206 (experimental) % make /bin/sh: line 1: 41686 Segmentation fault (core dumped) CC='gcc -pthread' LDSHARED='gcc -pthread -shared ' OPT='-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", line 62, in import os File "/net/theta/raid1/rwgk/junk/Python-2.7.1/Lib/os.py", line 743, in def urandom(n): SystemError: unknown opcode make: *** [sharedmods] Error 1 make finishes OK if I configure --with-pydebug. Therefore my guess is that there is an optimizer bug in the current gcc 4.6 that's only triggered by a specific construct in Python. (A lot of other stuff builds and runs fine.) 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. ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] devguide: Point out that OS X users need to change examples to use python.exe instead of
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 run in-place; ``./python`` on most machines, ``./python.exe`` >> -on OS X. >> +on OS X (all examples throughout this documentation say ``./python`` but >> +implies you choose the proper name based on your OS). > > That's true on OS X if you are using a case-insensitive file system. > But wIth the newer, case-sensitive HFS+, for example, you get ./python. Are you thinking of UFS, because I am running HFS+ and I still get python.exe since it's case-preserving. Regardless, I will add a note about the case-sensitivity. > > -- > Ned Deily, > [email protected] > > ___ > Python-Dev mailing list > [email protected] > http://mail.python.org/mailman/listinfo/python-dev > Unsubscribe: > http://mail.python.org/mailman/options/python-dev/brett%40python.org > ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] devguide: Point out that OS X users need to change examples to use python.exe instead of
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 will then have a working build of Python > >> that can be run in-place; ``./python`` on most machines, ``./python.exe`` > >> -on OS X. > >> +on OS X (all examples throughout this documentation say ``./python`` but > >> +implies you choose the proper name based on your OS). > > > > That's true on OS X if you are using a case-insensitive file system. > > But wIth the newer, case-sensitive HFS+, for example, you get ./python. > > Are you thinking of UFS, because I am running HFS+ and I still get > python.exe since it's case-preserving. No, not UFS. Since at least 10.4, OS X has supported the creation of at least four variants of HFS+ via Disk Utility.app or disktutil(8). The 10.6 version of diskutil added a handy way to list all available file systems: $ diskutil listFileSystems Formattable filesystems [...] PERSONALITY USER VISIBLE NAME [...] HFS+Mac OS Extended Case-sensitive HFS+ Mac OS Extended (Case-sensitive) (or) hfsx Case-sensitive Journaled HFS+ Mac OS Extended (Case-sensitive, Journaled) (or) jhfsx Journaled HFS+ Mac OS Extended (Journaled) (or) jhfs+ These days, one of the latter two is used to format the primary file system where OS X resides: I believe journaled is a requirement from at least 10.5 on, case-sensitive is optional. I've been using "jhfsx" for my primary development machine since 10.5 was released a few years ago. Since it is a file system type, AFAIK it is necessary to re-initialize the partition and reload files on it. > Regardless, I will add a note about the case-sensitivity. Thanks! -- Ned Deily, [email protected] ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] FYI: Python 2.7.1 + gcc 4.6 (experimental) probable optimizer problem
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 the gcc developers. By the way, can you try to build Python 3.2 too? ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] FYI: Python 2.7.1 + gcc 4.6 (experimental) probable optimizer problem
> 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 ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] FYI: Python 2.7.1 + gcc 4.6 (experimental) probable optimizer problem
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" mode. > > You should report a bug with the gcc developers. > By the way, can you try to build Python 3.2 too? I can reproduce this with release27-maint on Fedora-14/amd64/gcc-4.6. -fno-strict-aliasing is enabled. py3k is fine. Hard to tell if it's a gcc bug or not. gcc-4.6 increased the ANSI compliance requirements yet again, exposing third party bugs like this one: http://sourceware.org/ml/libc-alpha/2010-12/msg9.html There is an issue for this: http://bugs.python.org/issue9880 Stefan Krah ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] devguide: Add an intermediate task of helping triage issues (not to be confused with the
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 that can reproduce the bug? > + > +These are things anyone can help with. FWIW, I'm really not fond of handing out triage tasks to beginners. First because the claim that it doesn't require any specific knowledge is wrong (in the case of Python, because it is a highly technical product; it might be right for office suites, who knows). Second because a newbie triager gets to interact with other newbies who might be very confused if they are given misleading comments or asked misleading (or completely irrelevant) questions. Things may be different when the person in question has been a long-time community member, or has specific expertise, and is therefore able to communicate meaningful advice. But for true beginners, I think it would be much better to let them write a patch or a doc fix. Regards Antoine. ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] FYI: Python 2.7.1 + gcc 4.6 (experimental) probable optimizer problem
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 current gcc 4.6 svn. > > > Note that gcc 4.6 is now in "bug-fix only" mode. > > > > You should report a bug with the gcc developers. > > By the way, can you try to build Python 3.2 too? > > 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: > There is an issue for this: > > http://bugs.python.org/issue9880 Regards Antoine. ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] FYI: Python 2.7.1 + gcc 4.6 (experimental) probable optimizer problem
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: I narrowed the issue down to -ftree-vectorize, which is part of -O3. Searching briefly for 'ftree-vectorize + bug' makes me think that we should wait for the stable gcc-4.6. Stefan Krah ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] PEP 3333: wsgi_string() function
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 7-bit and 8-bit coded character sets -- Code extension techniques". The popularity of that standard speaks for itself. ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
