Mailman 3 November 2011 - Python-checkins

Re: [Python-checkins] cpython: pyexpat uses the new Unicode API
by Amaury Forgeot d'Arc 29 Jul '12

29 Jul '12

> changeset: 72548:a1be34457ccf > user: Victor Stinner <victor.stinner at haypocalc.com> > date: Sat Oct 01 01:05:40 2011 +0200 > summary: > pyexat uses the new Unicode API > > files: > Modules/pyexpat.c | 12 +++++++----- > 1 files changed, 7 insertions(+), 5 deletions(-) > > > diff --git a/Modules/pyexpat.c b/Modules/pyexpat.c > --- a/Modules/pyexpat.c > +++ b/Modules/pyexpat.c > @@ -1234,11 +1234,13 @@ > static PyObject * > xmlparse_getattro(xmlparseobject *self, PyObject *nameobj) > { > - const Py_UNICODE *name; > + Py_UCS4 first_char; > int handlernum = -1; > > if (!PyUnicode_Check(nameobj)) > goto generic; > + if (PyUnicode_READY(nameobj)) > + return NULL; Why is this PyUnicode_READY necessary? Can tp_getattro pass unfinished unicode objects? I hope we don't have to update all extension modules? -- Amaury Forgeot d'Arc

2 1

cpython: Credit Per Øyvind Karlsen for the initial implementation of the lzma module
by nadeem.vawda 30 Nov '11

30 Nov '11

http://hg.python.org/cpython/rev/6cde416ef03b changeset: 73798:6cde416ef03b user: Nadeem Vawda <nadeem.vawda(a)gmail.com> date: Thu Dec 01 01:18:27 2011 +0200 summary: Credit Per Øyvind Karlsen for the initial implementation of the lzma module (issue #6715). files: Misc/ACKS | 1 + Misc/NEWS | 1 + Modules/_lzmamodule.c | 7 ++++++- 3 files changed, 8 insertions(+), 1 deletions(-) diff --git a/Misc/ACKS b/Misc/ACKS --- a/Misc/ACKS +++ b/Misc/ACKS @@ -502,6 +502,7 @@ Peter van Kampen Rafe Kaplan Jacob Kaplan-Moss +Per Øyvind Karlsen Lou Kates Hiroaki Kawai Sebastien Keim diff --git a/Misc/NEWS b/Misc/NEWS --- a/Misc/NEWS +++ b/Misc/NEWS @@ -400,6 +400,7 @@ ------- - Issue #6715: Add a module 'lzma' for compression using the LZMA algorithm. + Thanks to Per Øyvind Karlsen for the initial implementation. - Issue #13487: Make inspect.getmodule robust against changes done to sys.modules while it is iterating over it. diff --git a/Modules/_lzmamodule.c b/Modules/_lzmamodule.c --- a/Modules/_lzmamodule.c +++ b/Modules/_lzmamodule.c @@ -1,4 +1,9 @@ -/* _lzma - Low-level Python interface to liblzma. */ +/* _lzma - Low-level Python interface to liblzma. + + Initial implementation by Per Øyvind Karlsen. + Rewritten by Nadeem Vawda. + +*/ #define PY_SSIZE_T_CLEAN -- Repository URL: http://hg.python.org/cpython

1 0

cpython (merge 3.2 -> default): Issue #1040439: better document how to compile and link an embedded Python
by antoine.pitrou 30 Nov '11

30 Nov '11

http://hg.python.org/cpython/rev/528abe272856 changeset: 73797:528abe272856 parent: 73795:354dc460cba5 parent: 73796:2c05b8a6cdd1 user: Antoine Pitrou <solipsis(a)pitrou.net> date: Wed Nov 30 21:20:01 2011 +0100 summary: Issue #1040439: better document how to compile and link an embedded Python interpreter. Still lacks docs for Windows (anyone?). files: Doc/extending/embedding.rst | 72 +++++++++++++++--------- 1 files changed, 44 insertions(+), 28 deletions(-) diff --git a/Doc/extending/embedding.rst b/Doc/extending/embedding.rst --- a/Doc/extending/embedding.rst +++ b/Doc/extending/embedding.rst @@ -133,8 +133,9 @@ This code loads a Python script using ``argv[1]``, and calls the function named in ``argv[2]``. Its integer arguments are the other values of the ``argv`` -array. If you compile and link this program (let's call the finished executable -:program:`call`), and use it to execute a Python script, such as:: +array. If you :ref:`compile and link <compiling>` this program (let's call +the finished executable :program:`call`), and use it to execute a Python +script, such as:: def multiply(a,b): print("Will compute", a, "times", b) @@ -257,37 +258,52 @@ program. There is no need to recompile Python itself using C++. -.. _link-reqs: +.. _compiling: -Linking Requirements -==================== +Compiling and Linking under Unix-like systems +============================================= -While the :program:`configure` script shipped with the Python sources will -correctly build Python to export the symbols needed by dynamically linked -extensions, this is not automatically inherited by applications which embed the -Python library statically, at least on Unix. This is an issue when the -application is linked to the static runtime library (:file:`libpython.a`) and -needs to load dynamic extensions (implemented as :file:`.so` files). +It is not necessarily trivial to find the right flags to pass to your +compiler (and linker) in order to embed the Python interpreter into your +application, particularly because Python needs to load library modules +implemented as C dynamic extensions (:file:`.so` files) linked against +it. -The problem is that some entry points are defined by the Python runtime solely -for extension modules to use. If the embedding application does not use any of -these entry points, some linkers will not include those entries in the symbol -table of the finished executable. Some additional options are needed to inform -the linker not to remove these symbols. +To find out the required compiler and linker flags, you can execute the +:file:`python{X.Y}-config` script which is generated as part of the +installation process (a generic :file:`python3-config` script is also +available). This script has several options, of which the following will +be directly useful to you: -Determining the right options to use for any given platform can be quite -difficult, but fortunately the Python configuration already has those values. -To retrieve them from an installed Python interpreter, start an interactive -interpreter and have a short session like this:: +* ``pythonX.Y-config --cflags`` will give you the recommended flags when + compiling:: - >>> import distutils.sysconfig - >>> distutils.sysconfig.get_config_var('LINKFORSHARED') + $ /opt/bin/python3.2-config --cflags + -I/opt/include/python3.2m -I/opt/include/python3.2m -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes + +* ``pythonX.Y-config --ldflags`` will give you the recommended flags when + linking:: + + $ /opt/bin/python3.2-config --ldflags + -I/opt/lib/python3.2/config-3.2m -lpthread -ldl -lutil -lm -lpython3.2m -Xlinker -export-dynamic + +.. note:: + To avoid confusion between several Python installations (and especially + between the system Python and your own compiled Python), it is recommended + that you use the absolute path to :file:`python{X.Y}-config`, as in the above + example. + +If this procedure doesn't work for you (it is not guaranteed to work for +all Unix-like platforms; however, we welcome bug reports at +http://bugs.python.org), you will have to read your system's documentation +about dynamic linking and/or examine Python's Makefile and compilation +options. In this case, the :mod:`sysconfig` module is a useful tool to +programmatically extract the configuration values that you will want to +combine together:: + + >>> import sysconfig + >>> sysconfig.get_config_var('LINKFORSHARED') '-Xlinker -export-dynamic' -.. index:: module: distutils.sysconfig -The contents of the string presented will be the options that should be used. -If the string is empty, there's no need to add any additional options. The -:const:`LINKFORSHARED` definition corresponds to the variable of the same name -in Python's top-level :file:`Makefile`. - +.. XXX similar documentation for Windows missing -- Repository URL: http://hg.python.org/cpython

1 0

cpython (3.2): Issue #1040439: better document how to compile and link an embedded Python
by antoine.pitrou 30 Nov '11

30 Nov '11

http://hg.python.org/cpython/rev/2c05b8a6cdd1 changeset: 73796:2c05b8a6cdd1 branch: 3.2 parent: 73789:2ef359d7a2e9 user: Antoine Pitrou <solipsis(a)pitrou.net> date: Wed Nov 30 21:19:21 2011 +0100 summary: Issue #1040439: better document how to compile and link an embedded Python interpreter. Still lacks docs for Windows (anyone?). files: Doc/extending/embedding.rst | 72 +++++++++++++++--------- 1 files changed, 44 insertions(+), 28 deletions(-) diff --git a/Doc/extending/embedding.rst b/Doc/extending/embedding.rst --- a/Doc/extending/embedding.rst +++ b/Doc/extending/embedding.rst @@ -133,8 +133,9 @@ This code loads a Python script using ``argv[1]``, and calls the function named in ``argv[2]``. Its integer arguments are the other values of the ``argv`` -array. If you compile and link this program (let's call the finished executable -:program:`call`), and use it to execute a Python script, such as:: +array. If you :ref:`compile and link <compiling>` this program (let's call +the finished executable :program:`call`), and use it to execute a Python +script, such as:: def multiply(a,b): print("Will compute", a, "times", b) @@ -257,37 +258,52 @@ program. There is no need to recompile Python itself using C++. -.. _link-reqs: +.. _compiling: -Linking Requirements -==================== +Compiling and Linking under Unix-like systems +============================================= -While the :program:`configure` script shipped with the Python sources will -correctly build Python to export the symbols needed by dynamically linked -extensions, this is not automatically inherited by applications which embed the -Python library statically, at least on Unix. This is an issue when the -application is linked to the static runtime library (:file:`libpython.a`) and -needs to load dynamic extensions (implemented as :file:`.so` files). +It is not necessarily trivial to find the right flags to pass to your +compiler (and linker) in order to embed the Python interpreter into your +application, particularly because Python needs to load library modules +implemented as C dynamic extensions (:file:`.so` files) linked against +it. -The problem is that some entry points are defined by the Python runtime solely -for extension modules to use. If the embedding application does not use any of -these entry points, some linkers will not include those entries in the symbol -table of the finished executable. Some additional options are needed to inform -the linker not to remove these symbols. +To find out the required compiler and linker flags, you can execute the +:file:`python{X.Y}-config` script which is generated as part of the +installation process (a generic :file:`python3-config` script is also +available). This script has several options, of which the following will +be directly useful to you: -Determining the right options to use for any given platform can be quite -difficult, but fortunately the Python configuration already has those values. -To retrieve them from an installed Python interpreter, start an interactive -interpreter and have a short session like this:: +* ``pythonX.Y-config --cflags`` will give you the recommended flags when + compiling:: - >>> import distutils.sysconfig - >>> distutils.sysconfig.get_config_var('LINKFORSHARED') + $ /opt/bin/python3.2-config --cflags + -I/opt/include/python3.2m -I/opt/include/python3.2m -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes + +* ``pythonX.Y-config --ldflags`` will give you the recommended flags when + linking:: + + $ /opt/bin/python3.2-config --ldflags + -I/opt/lib/python3.2/config-3.2m -lpthread -ldl -lutil -lm -lpython3.2m -Xlinker -export-dynamic + +.. note:: + To avoid confusion between several Python installations (and especially + between the system Python and your own compiled Python), it is recommended + that you use the absolute path to :file:`python{X.Y}-config`, as in the above + example. + +If this procedure doesn't work for you (it is not guaranteed to work for +all Unix-like platforms; however, we welcome bug reports at +http://bugs.python.org), you will have to read your system's documentation +about dynamic linking and/or examine Python's Makefile and compilation +options. In this case, the :mod:`sysconfig` module is a useful tool to +programmatically extract the configuration values that you will want to +combine together:: + + >>> import sysconfig + >>> sysconfig.get_config_var('LINKFORSHARED') '-Xlinker -export-dynamic' -.. index:: module: distutils.sysconfig -The contents of the string presented will be the options that should be used. -If the string is empty, there's no need to add any additional options. The -:const:`LINKFORSHARED` definition corresponds to the variable of the same name -in Python's top-level :file:`Makefile`. - +.. XXX similar documentation for Windows missing -- Repository URL: http://hg.python.org/cpython

1 0

cpython: Make error handling in BZ2File.{readable,seekable,writable,fileno} consistent
by nadeem.vawda 30 Nov '11

30 Nov '11

http://hg.python.org/cpython/rev/354dc460cba5 changeset: 73795:354dc460cba5 user: Nadeem Vawda <nadeem.vawda(a)gmail.com> date: Wed Nov 30 17:39:30 2011 +0200 summary: Make error handling in BZ2File.{readable,seekable,writable,fileno} consistent with TextIOWrapper. Also, add tests for these methods. files: Lib/bz2.py | 6 +- Lib/test/test_bz2.py | 57 +++++++++++++++++++++++++++++++- 2 files changed, 59 insertions(+), 4 deletions(-) diff --git a/Lib/bz2.py b/Lib/bz2.py --- a/Lib/bz2.py +++ b/Lib/bz2.py @@ -125,6 +125,7 @@ def fileno(self): """Return the file descriptor for the underlying file.""" + self._check_not_closed() return self._fp.fileno() def seekable(self): @@ -133,10 +134,12 @@ def readable(self): """Return whether the file was opened for reading.""" + self._check_not_closed() return self._mode in (_MODE_READ, _MODE_READ_EOF) def writable(self): """Return whether the file was opened for writing.""" + self._check_not_closed() return self._mode == _MODE_WRITE # Mode-checking helper functions. @@ -147,17 +150,14 @@ def _check_can_read(self): if not self.readable(): - self._check_not_closed() raise io.UnsupportedOperation("File not open for reading") def _check_can_write(self): if not self.writable(): - self._check_not_closed() raise io.UnsupportedOperation("File not open for writing") def _check_can_seek(self): if not self.seekable(): - self._check_not_closed() raise io.UnsupportedOperation("Seeking is only supported " "on files open for reading") diff --git a/Lib/test/test_bz2.py b/Lib/test/test_bz2.py --- a/Lib/test/test_bz2.py +++ b/Lib/test/test_bz2.py @@ -348,8 +348,63 @@ def testFileno(self): self.createTempFile() with open(self.filename, 'rb') as rawf: - with BZ2File(fileobj=rawf) as bz2f: + bz2f = BZ2File(fileobj=rawf) + try: self.assertEqual(bz2f.fileno(), rawf.fileno()) + finally: + bz2f.close() + self.assertRaises(ValueError, bz2f.fileno) + + def testSeekable(self): + bz2f = BZ2File(fileobj=BytesIO(self.DATA)) + try: + self.assertTrue(bz2f.seekable()) + bz2f.read() + self.assertTrue(bz2f.seekable()) + finally: + bz2f.close() + self.assertRaises(ValueError, bz2f.seekable) + + bz2f = BZ2File(fileobj=BytesIO(), mode="w") + try: + self.assertFalse(bz2f.seekable()) + finally: + bz2f.close() + self.assertRaises(ValueError, bz2f.seekable) + + def testReadable(self): + bz2f = BZ2File(fileobj=BytesIO(self.DATA)) + try: + self.assertTrue(bz2f.readable()) + bz2f.read() + self.assertTrue(bz2f.readable()) + finally: + bz2f.close() + self.assertRaises(ValueError, bz2f.readable) + + bz2f = BZ2File(fileobj=BytesIO(), mode="w") + try: + self.assertFalse(bz2f.readable()) + finally: + bz2f.close() + self.assertRaises(ValueError, bz2f.readable) + + def testWritable(self): + bz2f = BZ2File(fileobj=BytesIO(self.DATA)) + try: + self.assertFalse(bz2f.writable()) + bz2f.read() + self.assertFalse(bz2f.writable()) + finally: + bz2f.close() + self.assertRaises(ValueError, bz2f.writable) + + bz2f = BZ2File(fileobj=BytesIO(), mode="w") + try: + self.assertTrue(bz2f.writable()) + finally: + bz2f.close() + self.assertRaises(ValueError, bz2f.writable) def testOpenDel(self): self.createTempFile() -- Repository URL: http://hg.python.org/cpython

1 0

distutils2: Typos
by eric.araujo 30 Nov '11

30 Nov '11

http://hg.python.org/distutils2/rev/5281c4d4075f changeset: 1268:5281c4d4075f parent: 1266:3f8b40403811 user: Éric Araujo <merwok(a)netwok.org> date: Wed Nov 30 13:24:44 2011 +0100 summary: Typos files: distutils2/pypi/dist.py | 2 +- distutils2/pypi/simple.py | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/distutils2/pypi/dist.py b/distutils2/pypi/dist.py --- a/distutils2/pypi/dist.py +++ b/distutils2/pypi/dist.py @@ -430,7 +430,7 @@ """Sort the results with the given properties. The `prefer_final` argument can be used to specify if final - distributions (eg. not dev, bet or alpha) would be prefered or not. + distributions (eg. not dev, beta or alpha) would be preferred or not. Results can be inverted by using `reverse`. diff --git a/distutils2/pypi/simple.py b/distutils2/pypi/simple.py --- a/distutils2/pypi/simple.py +++ b/distutils2/pypi/simple.py @@ -273,7 +273,7 @@ def _register_release(self, release=None, release_info={}): """Register a new release. - Both a release or a dict of release_info can be provided, the prefered + Both a release or a dict of release_info can be provided, the preferred way (eg. the quicker) is the dict one. Return the list of existing releases for the given project. -- Repository URL: http://hg.python.org/distutils2

1 0

distutils2: Update list of trove classifiers
by eric.araujo 30 Nov '11

30 Nov '11

http://hg.python.org/distutils2/rev/42342803970e changeset: 1269:42342803970e user: Éric Araujo <merwok(a)netwok.org> date: Wed Nov 30 13:30:20 2011 +0100 summary: Update list of trove classifiers files: distutils2/_trove.py | 12 ++++++++++++ 1 files changed, 12 insertions(+), 0 deletions(-) diff --git a/distutils2/_trove.py b/distutils2/_trove.py --- a/distutils2/_trove.py +++ b/distutils2/_trove.py @@ -47,6 +47,12 @@ 'Framework :: IDLE', 'Framework :: Paste', 'Framework :: Plone', +'Framework :: Plone :: 3.2', +'Framework :: Plone :: 3.3', +'Framework :: Plone :: 4.0', +'Framework :: Plone :: 4.1', +'Framework :: Plone :: 4.2', +'Framework :: Plone :: 4.3', 'Framework :: Pylons', 'Framework :: Setuptools Plugin', 'Framework :: Trac', @@ -261,6 +267,12 @@ 'Programming Language :: Python :: 3.0', 'Programming Language :: Python :: 3.1', 'Programming Language :: Python :: 3.2', +'Programming Language :: Python :: Implementation', +'Programming Language :: Python :: Implementation :: CPython', +'Programming Language :: Python :: Implementation :: IronPython', +'Programming Language :: Python :: Implementation :: Jython', +'Programming Language :: Python :: Implementation :: PyPy', +'Programming Language :: Python :: Implementation :: Stackless', 'Programming Language :: REBOL', 'Programming Language :: Rexx', 'Programming Language :: Ruby', -- Repository URL: http://hg.python.org/distutils2

1 0

Daily reference leaks (5d42f22189be): sum=0
by solipsis＠pitrou.net 29 Nov '11

29 Nov '11

results for 5d42f22189be on branch "default" -------------------------------------------- Command line was: ['./python', '-m', 'test.regrtest', '-uall', '-R', '3:3:/home/antoine/cpython/refleaks/refloghzzVTc', '-x']

1 0

peps: Typo in PEP 393
by jesus.cea 29 Nov '11

29 Nov '11

http://hg.python.org/peps/rev/37ae67559050 changeset: 4005:37ae67559050 user: Jesus Cea <jcea(a)jcea.es> date: Wed Nov 30 03:35:05 2011 +0100 summary: Typo in PEP 393 files: pep-0393.txt | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/pep-0393.txt b/pep-0393.txt --- a/pep-0393.txt +++ b/pep-0393.txt @@ -189,7 +189,7 @@ gives the void pointer to the data. Access to individual characters should use PyUnicode_{READ|WRITE}[_CHAR]: - - PyUnciode_READ(kind, data, index) + - PyUnicode_READ(kind, data, index) - PyUnicode_WRITE(kind, data, index, value) - PyUnicode_READ_CHAR(unicode, index) -- Repository URL: http://hg.python.org/peps

1 0

devguide: Add entry for new lzma module to experts.rst.
by nadeem.vawda 29 Nov '11

29 Nov '11

http://hg.python.org/devguide/rev/3f6ae39917cd changeset: 464:3f6ae39917cd user: Nadeem Vawda <nadeem.vawda(a)gmail.com> date: Wed Nov 30 00:08:59 2011 +0200 summary: Add entry for new lzma module to experts.rst. files: experts.rst | 1 + 1 files changed, 1 insertions(+), 0 deletions(-) diff --git a/experts.rst b/experts.rst --- a/experts.rst +++ b/experts.rst @@ -137,6 +137,7 @@ linecache locale loewis, lemburg logging vinay.sajip +lzma nadeem.vawda macpath mailbox mailcap -- Repository URL: http://hg.python.org/devguide

1 0