Re: [Python-Dev] r85559 - in python/branches/py3k: Doc/library/sys.rst Lib/distutils/command/build_ext.py Lib/distutils/tests/test_build_ext.py Lib/test/test_sys.py Makefile.pre.in Misc/python-config.
Am 16.10.2010 03:04, schrieb barry.warsaw: Author: barry.warsaw Date: Sat Oct 16 03:04:07 2010 New Revision: 85559 Log: First (uncontroversial) part of issue 9807. * Expose the build flags to Python as sys.abiflags * Shared library libpythonX.Yabiflags.so * python-config --abiflags * Make two distutils tests that failed with --enable-shared (even before this patch) succeed. * Fix a few small style issues. Modified: python/branches/py3k/Doc/library/sys.rst python/branches/py3k/Lib/distutils/command/build_ext.py python/branches/py3k/Lib/distutils/tests/test_build_ext.py python/branches/py3k/Lib/test/test_sys.py python/branches/py3k/Makefile.pre.in python/branches/py3k/Misc/python-config.in python/branches/py3k/Python/sysmodule.c python/branches/py3k/configure python/branches/py3k/configure.in Modified: python/branches/py3k/Doc/library/sys.rst == --- python/branches/py3k/Doc/library/sys.rst (original) +++ python/branches/py3k/Doc/library/sys.rst Sat Oct 16 03:04:07 2010 @@ -955,6 +955,11 @@ module for informational purposes; modifying this value has no effect on the registry keys used by Python. Availability: Windows. +.. data:: abiflags + + On POSIX systems where Python is build with the standard ``configure`` + script, this contains the ABI flags as specified by :pep:`3149`. + Needs a versionadded. Also, I think we at least tried to maintain a rough alphabetical order of sys members... 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. ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] r85559 - in python/branches/py3k: Doc/library/sys.rst Lib/distutils/command/build_ext.py Lib/distutils/tests/test_build_ext.py Lib/test/test_sys.py Makefile.pre.in Misc/python-config.
On Oct 16, 2010, at 01:50 PM, Georg Brandl wrote: --- python/branches/py3k/Doc/library/sys.rst (original) +++ python/branches/py3k/Doc/library/sys.rst Sat Oct 16 03:04:07 2010 @@ -955,6 +955,11 @@ module for informational purposes; modifying this value has no effect on the registry keys used by Python. Availability: Windows. +.. data:: abiflags + + On POSIX systems where Python is build with the standard ``configure`` + script, this contains the ABI flags as specified by :pep:`3149`. + Needs a versionadded. Also, I think we at least tried to maintain a rough alphabetical order of sys members... Thanks, good catch. r85571 -Barry signature.asc Description: PGP signature ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] r85569 - in python/branches/py3k: Misc/NEWS Parser/tokenizer.h Python/ast.c Python/bltinmodule.c Python/compile.c Python/pythonrun.c Python/traceback.c
On Sat, 16 Oct 2010 15:14:10 +0200 (CEST) victor.stinner python-check...@python.org wrote: Author: victor.stinner Date: Sat Oct 16 15:14:10 2010 New Revision: 85569 Log: Issue #9713, #10114: Parser functions (eg. PyParser_ASTFromFile) expects filenames encoded to the filesystem encoding with surrogateescape error handler (to support undecodable bytes), instead of UTF-8 in strict mode. This change broke at least two buildbots: http://www.python.org/dev/buildbot/builders/AMD64%20Gentoo%20Wide%203.x http://www.python.org/dev/buildbot/builders/sparc%20solaris10%20gcc%203.x cheers Antoine. ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
[Python-Dev] PPC Leopard buildbot failing sqlite test for Python 3.2
There was a test added to the sqlite suite between 3.1 and the current 3.x trunk, TestInTransaction. It's failing pretty consistently on the PPC Leopard buildbot (2.7 and 3.1 are testing OK). Calling sqlite3.sqlite_version returns 3.4.0. A couple of things come to mind: * Does this require a different flavor of the sqlite libraries? I looked through the 3.x docs and couldn't find any mention of a specific sqlite version. * Is this a big-endian bug? Might fail on SPARC, too, then. What should I look at? Bill ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] PPC Leopard buildbot failing sqlite test for Python 3.2
On Sat, 16 Oct 2010 13:14:20 -0700, Bill Janssen jans...@parc.com wrote: There was a test added to the sqlite suite between 3.1 and the current 3.x trunk, TestInTransaction. It's failing pretty consistently on the PPC Leopard buildbot (2.7 and 3.1 are testing OK). Calling sqlite3.sqlite_version returns 3.4.0. A couple of things come to mind: * Does this require a different flavor of the sqlite libraries? I looked through the 3.x docs and couldn't find any mention of a specific sqlite version. That's what I was wondering (I see you found the relevant issue...), but it doesn't *seem* to be a version issue, but it would be cool if you could check it against 3.7 just for confirmation. * Is this a big-endian bug? Might fail on SPARC, too, then. It might be, except for two things: it passes on the Sparc Solaris 10 buildbot, and the io module also makes use of a T_BOOL field and its tests pass on all buildbots. On the flip side, the only other failure I've see was on the Debian Sparc buildbot. Which claims it is running sqlite 3.7.2-1. It works for me using 3.7.2 on Gentoo i86. What should I look at? Good question :) When I added this it seemed like such a simple thing. Maybe the endianness issue is the one to look at, despite the pass on Solaris. -- R. David Murray www.bitdance.com ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] r85569 - in python/branches/py3k: Misc/NEWS Parser/tokenizer.h Python/ast.c Python/bltinmodule.c Python/compile.c Python/pythonrun.c Python/traceback.c
Hi, Le samedi 16 octobre 2010 18:26:31, Antoine Pitrou a écrit : On Sat, 16 Oct 2010 15:14:10 +0200 (CEST) victor.stinner python-check...@python.org wrote: Author: victor.stinner Date: Sat Oct 16 15:14:10 2010 New Revision: 85569 Log: Issue #9713, #10114: Parser functions (eg. PyParser_ASTFromFile) expects filenames encoded to the filesystem encoding with surrogateescape error handler (to support undecodable bytes), instead of UTF-8 in strict mode. This change broke at least two buildbots: http://www.python.org/dev/buildbot/builders/AMD64%20Gentoo%20Wide%203.x http://www.python.org/dev/buildbot/builders/sparc%20solaris10%20gcc%203.x Yeah, I already noticed that. I added comments to #10114, and then opened issue #10123. #10123 should be fixed by r85578. -- Victor Stinner http://www.haypocalc.com/ ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] PPC Leopard buildbot failing sqlite test for Python 3.2
R. David Murray rdmur...@bitdance.com wrote: On Sat, 16 Oct 2010 13:14:20 -0700, Bill Janssen jans...@parc.com wrote: There was a test added to the sqlite suite between 3.1 and the current 3.x trunk, TestInTransaction. It's failing pretty consistently on the PPC Leopard buildbot (2.7 and 3.1 are testing OK). Calling sqlite3.sqlite_version returns 3.4.0. A couple of things come to mind: * Does this require a different flavor of the sqlite libraries? I looked through the 3.x docs and couldn't find any mention of a specific sqlite version. That's what I was wondering (I see you found the relevant issue...), but it doesn't *seem* to be a version issue, but it would be cool if you could check it against 3.7 just for confirmation. * Is this a big-endian bug? Might fail on SPARC, too, then. It might be, except for two things: it passes on the Sparc Solaris 10 buildbot, For 3.x, the SPARC Solaris gcc buildbot says, [ 87/349] test_sqlite test_sqlite skipped -- No module named _sqlite3 and the io module also makes use of a T_BOOL field and its tests pass on all buildbots. On the flip side, the only other failure I've see was on the Debian Sparc buildbot. Which claims it is running sqlite 3.7.2-1. It works for me using 3.7.2 on Gentoo i86. What should I look at? Good question :) When I added this it seemed like such a simple thing. Maybe the endianness issue is the one to look at, despite the pass on Solaris. The SPARC architecture supports either big-endian and little-endian use (as does the PowerPC -- actually, I think any program can switch endianness on the PowerPC, except...); the OS gets to decide. I'd expect Solaris on SPARC to run big-endian, like OS X on PPC, and Wikipedia says Ubuntu on SPARC runs big-endian, too. Except: PPC Leopard is running on a G5 process, a PowerPC 970. As far as I know, that's the only PowerPC chip that couldn't run either-endian -- it only runs big-endian. So that code has to be running big-endian on PPC Leopard. Looks like it's not passing on any big-endian architecture. Bill ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
