Python-Dev April 2012

python-dev@python.org

98 participants
125 discussions

Re: [Python-Dev] [Python-checkins] cpython: Fix #3561. Add an option to place the Python installation into the Windows Path
by Brian Curtin 25 Apr '12

25 Apr '12

On Wed, Apr 25, 2012 at 08:13, brian.curtin <python-checkins(a)python.org> wrote: > http://hg.python.org/cpython/rev/4e9f1017355f > changeset: 76556:4e9f1017355f > user: Brian Curtin <brian(a)python.org> > date: Wed Apr 25 08:12:37 2012 -0500 > summary: > Fix #3561. Add an option to place the Python installation into the Windows Path environment variable. > > files: > Misc/NEWS | 3 +++ > Tools/msi/msi.py | 22 +++++++++++++++++++--- > 2 files changed, 22 insertions(+), 3 deletions(-) http://bugs.python.org/issue14668 was created for updating the relevant documentation. I pushed without docs since it's unlikely they'll be done before the weekend's alpha 3 build, and I didn't want to have this feature wait an extra month before anyone sees it. Anyone who's installing an alpha build is probably advanced enough to know what it's doing in the meantime.

1 0

Building against system expat
by Bohuslav Kabrda 25 Apr '12

25 Apr '12

Hi, I'm trying to build Python 3.2.3 against system expat library, that lies out of the ordinary directory structure (under /opt). I also have an older version of expat library in the system. No matter what shell variables or options I pass to configure and make, pyexpat gets linked against the system expat, which results in errors during tests: pyexpat.cpython-32dmu.so: undefined symbol: XML_SetHashSalt anyone has any idea what to pass to configure/make to link pyexpat with the other expat? Thanks! -- Regards, Bohuslav "Slavek" Kabrda.

1 0

Re: [Python-Dev] [Python-checkins] Daily reference leaks (a2cf07135e4f): sum=6
by Mark Shannon 25 Apr '12

25 Apr '12

solipsis(a)pitrou.net wrote: > results for a2cf07135e4f on branch "default" > -------------------------------------------- > > test_tempfile leaked [2, 2, 2] references, sum=6 > These leaks are due to 6e5855854a2e: “Implement PEP 412: Key-sharing dictionaries (closes #13903)”. They both occur in tests for tempfile.TemporaryDirectory, although I don't know what is special about that code. I'll investigate further when I have time. Cheers, Mark.

1 0

Re: [Python-Dev] [Python-checkins] peps: Note that ImportError will no longer be raised due to a missing __init__.py
by Brett Cannon 25 Apr '12

25 Apr '12

It's actually an ImportWarning, not Error (or at least that's what I meant on import-sig). If the module is eventually found then there is no error. On Thu, Apr 19, 2012 at 18:56, eric.smith <python-checkins(a)python.org>wrote: > http://hg.python.org/peps/rev/af61fe9a56fb > changeset: 4281:af61fe9a56fb > user: Eric V. Smith <eric(a)trueblade.com> > date: Thu Apr 19 18:56:22 2012 -0400 > summary: > Note that ImportError will no longer be raised due to a missing > __init__.py file. > > files: > pep-0420.txt | 5 +++++ > 1 files changed, 5 insertions(+), 0 deletions(-) > > > diff --git a/pep-0420.txt b/pep-0420.txt > --- a/pep-0420.txt > +++ b/pep-0420.txt > @@ -148,6 +148,11 @@ > path. With namespace packages, all entries in the path must be > scanned. > > +Note that an ImportError will no longer be raised for a directory > +lacking an ``__init__.py`` file. Such a directory will now be imported > +as a namespace package, whereas in prior Python versions an > +ImportError would be raised. > + > At PyCon 2012, we had a discussion about namespace packages at which > PEP 382 and PEP 402 were rejected, to be replaced by this PEP [1]_. > > > -- > Repository URL: http://hg.python.org/peps > > _______________________________________________ > Python-checkins mailing list > Python-checkins(a)python.org > http://mail.python.org/mailman/listinfo/python-checkins > >

5 4

Repeated hangs during "make test"
by Edward C. Jones 25 Apr '12

25 Apr '12

CPython 3.3.0a2 (default, Apr 24 2012, 10:47:03) [GCC 4.4.5] Linux-2.6.32-5-amd64-x86_64-with-debian-6.0.4 little-endian Ran "make test". Hung during test_socket. Used CNTL-C to exit the test. test_ssl failed. Ran "./python -m test -v test_ssl". Test ok. Ran "./python -m test -v test_socket" which was ok. Ran "make test" again. Hung during test_concurrent_futures. Used CNTL-C to exit test_concurrent_futures. test_ssl failed. Ran "./python -m test -v test_ssl". Test ok. Ran "make test" a third time. Hung during test_io. Used CNTL-C to exit test_io. test_ssl failed. Ran "./python -m test -v test_ssl". Test ok. Did it again. Same behavior except the hang is in test_buffer. And again for test_httpservers. What is going on?

3 2

Re: [Python-Dev] [Python-checkins] cpython: Closes Issue #14661: posix module: add O_EXEC, O_SEARCH, O_TTY_INIT (I add some
by Victor Stinner 25 Apr '12

25 Apr '12

2012/4/24 jesus.cea <python-checkins(a)python.org>: > http://hg.python.org/cpython/rev/2023f48b32b6 > changeset: 76537:2023f48b32b6 > user: Jesus Cea <jcea(a)jcea.es> > date: Tue Apr 24 20:59:17 2012 +0200 > summary: > Closes Issue #14661: posix module: add O_EXEC, O_SEARCH, O_TTY_INIT (I add some Solaris constants too) Don't you want to document these new constants in Doc/library/os.rst? Victor

1 0

Re: [Python-Dev] [Python-checkins] cpython (3.2): don't use a slot wrapper from a different special method (closes #14658)
by Mark Shannon 25 Apr '12

25 Apr '12

I'm not happy with this fix. Admittedly code like: class S(str): __getattr__ = str.__add__ s = S('a') print(S.b) is a little weird. But I think it should work (ie print 'ab') properly. This works without the patch. class S(str): __getattribute__ = str.__add__ s = S('a') print(S.b) (Prints 'ab') Also "slot wrapper" is a low-level implementation detail and shouldn't impact the language semantics. dict.__getitem__ is a slot wrapper; dict.__getitem__ is not. str.__getitem__ is a slot wrapper; list.__getitem__ is not. If any of these change then the semantics of the language changes. Cheers, Mark benjamin.peterson wrote: > http://hg.python.org/cpython/rev/971865f12377 > changeset: 76518:971865f12377 > branch: 3.2 > parent: 76506:f7b002e5cac7 > user: Benjamin Peterson <benjamin(a)python.org> > date: Tue Apr 24 11:06:25 2012 -0400 > summary: > don't use a slot wrapper from a different special method (closes #14658) > > This also alters the fix to #11603. Specifically, setting __repr__ to > object.__str__ now raises a recursion RuntimeError when str() or repr() is > called instead of silently bypassing the recursion. I believe this behavior is > more correct. > > files: > Lib/test/test_descr.py | 10 +++++++++- > Misc/NEWS | 6 ++++++ > Objects/typeobject.c | 5 +++-- > 3 files changed, 18 insertions(+), 3 deletions(-) > > > diff --git a/Lib/test/test_descr.py b/Lib/test/test_descr.py > --- a/Lib/test/test_descr.py > +++ b/Lib/test/test_descr.py > @@ -4430,7 +4430,15 @@ > pass > Foo.__repr__ = Foo.__str__ > foo = Foo() > - str(foo) > + self.assertRaises(RuntimeError, str, foo) > + self.assertRaises(RuntimeError, repr, foo) > + > + def test_mixing_slot_wrappers(self): > + class X(dict): > + __setattr__ = dict.__setitem__ > + x = X() > + x.y = 42 > + self.assertEqual(x["y"], 42) > > def test_cycle_through_dict(self): > # See bug #1469629 > diff --git a/Misc/NEWS b/Misc/NEWS > --- a/Misc/NEWS > +++ b/Misc/NEWS > @@ -10,6 +10,12 @@ > Core and Builtins > ----------------- > > +- Issue #11603 (again): Setting __repr__ to __str__ now raises a RuntimeError > + when repr() or str() is called on such an object. > + > +- Issue #14658: Fix binding a special method to a builtin implementation of a > + special method with a different name. > + > - Issue #14630: Fix a memory access bug for instances of a subclass of int > with value 0. > > diff --git a/Objects/typeobject.c b/Objects/typeobject.c > --- a/Objects/typeobject.c > +++ b/Objects/typeobject.c > @@ -2928,7 +2928,7 @@ > unaryfunc f; > > f = Py_TYPE(self)->tp_repr; > - if (f == NULL || f == object_str) > + if (f == NULL) > f = object_repr; > return f(self); > } > @@ -5757,7 +5757,8 @@ > } > continue; > } > - if (Py_TYPE(descr) == &PyWrapperDescr_Type) { > + if (Py_TYPE(descr) == &PyWrapperDescr_Type && > + ((PyWrapperDescrObject *)descr)->d_base->name_strobj == p->name_strobj) { > void **tptr = resolve_slotdups(type, p->name_strobj); > if (tptr == NULL || tptr == ptr) > generic = p->function; > > > > ------------------------------------------------------------------------ > > _______________________________________________ > Python-checkins mailing list > Python-checkins(a)python.org > http://mail.python.org/mailman/listinfo/python-checkins

3 4

Re: [Python-Dev] cpython: Closes Issue #14661: posix module: add O_EXEC, O_SEARCH, O_TTY_INIT (I add some
by Antoine Pitrou 25 Apr '12

25 Apr '12

On Tue, 24 Apr 2012 21:00:49 +0200 jesus.cea <python-checkins(a)python.org> wrote: > http://hg.python.org/cpython/rev/2023f48b32b6 > changeset: 76537:2023f48b32b6 > user: Jesus Cea <jcea(a)jcea.es> > date: Tue Apr 24 20:59:17 2012 +0200 > summary: > Closes Issue #14661: posix module: add O_EXEC, O_SEARCH, O_TTY_INIT (I add some Solaris constants too) Could you please add a Misc/NEWS entry for all this? Thank you Antoine.

2 1

Re: [Python-Dev] cpython (2.7): #14538: HTMLParser can now parse correctly start tags that contain a bare /.
by Georg Brandl 25 Apr '12

25 Apr '12

On 19.04.2012 03:36, ezio.melotti wrote: > http://hg.python.org/cpython/rev/36c901fcfcda > changeset: 76413:36c901fcfcda > branch: 2.7 > user: Ezio Melotti <ezio.melotti(a)gmail.com> > date: Wed Apr 18 19:08:41 2012 -0600 > summary: > #14538: HTMLParser can now parse correctly start tags that contain a bare /. > diff --git a/Misc/NEWS b/Misc/NEWS > --- a/Misc/NEWS > +++ b/Misc/NEWS > @@ -50,6 +50,9 @@ > Library > ------- > > +- Issue #14538: HTMLParser can now parse correctly start tags that contain > + a bare '/'. > + I think that's misleading: there's no way to "correctly" parse malformed HTML. Georg

5 6

What do PyAPI_FUNC & PyAPI_DATA mean?
by Mark Shannon 25 Apr '12

25 Apr '12

Many (most?) of the function declarations in the CPython header files are annotated with the PyAPI_FUNC declaration. Similarly for data declarations and PyAPI_DATA What do they mean, exactly? From the name I would expect that they are a way of declaring a function or datum to be part of the API, but their usage seems to be more to do with linkage. The reason I am asking is that the new dictionary implementation declares a few functions used to communicate between dictobject.c, typeobject.c and ceval.c which cannot be static functions, but are not intended to be part of the API. Cheers, Mark.

5 8

← Newer
1
2
3
4
5
6
7
...
13
Older →

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

1999

Python-Dev April 2012