Re: [Python-Dev] Copyediting PEPs
On Wed, Aug 29, 2012 at 2:45 PM, Guido van Rossum wrote: > Hm. I would be fine with the edits proposed, no need to bother others. But > please do use the Hg repo. :-) What? It's in Hg and I've been using Subversion all this time? Oh, you had my hopes up for a while there. Alas, the problem is that I didn't say clearly enough. I have access to the pydotorg svn repo, but not to anything beyond that. The error was that I thought that PEPs were in the web site repository, which they appear not to be. So it looks like I can't copyedit anyway. Sorry for the confusion! ChrisA ___ 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] [Python-checkins] cpython (merge 3.2 -> default): merge 3.2 (#15801)
Hi, benjamin.peterson wrote: > http://hg.python.org/cpython/rev/263d09ce3e9e > changeset: 78794:263d09ce3e9e > parent: 78790:454dceb5fd56 > parent: 78793:4d431e719646 > user:Benjamin Peterson > date:Tue Aug 28 18:01:45 2012 -0400 > summary: > merge 3.2 (#15801) > > files: > Lib/test/string_tests.py | 3 +++ > Misc/NEWS| 3 +++ > Objects/unicodeobject.c | 3 +-- > 3 files changed, 7 insertions(+), 2 deletions(-) > [snip] > diff --git a/Misc/NEWS b/Misc/NEWS > --- a/Misc/NEWS > +++ b/Misc/NEWS > @@ -71,6 +71,9 @@ > > - Issue #15761: Fix crash when PYTHONEXECUTABLE is set on Mac OS X. > > +- Issue #15801: Make sure mappings passed to '%' formatting are actually > + subscriptable. > + > - Issue #15726: Fix incorrect bounds checking in PyState_FindModule. >Patch by Robin Schreiber. The news entry was added in the middle of the news for 3.3.0 RC 1, which has already been released. Petri ___ 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] core dev IRC nicks
On Tue, 28 Aug 2012 23:21:15 -0500, Brian Curtin wrote: > On Tue, Aug 28, 2012 at 10:58 PM, Chris Jerdonek > wrote: > > Is there a list somewhere of the IRC nicks of the core developers that > > use IRC (and who wish to be listed) alongside their real names? If > > there is no such list, has there ever been discussion on python-dev of > > creating such a list? > > I'm sure we could make one, but it's probably of limited utility since > not many people are on IRC, and those who are come and go throughout > the day, throughout the month, year, etc. > > It'd just end up being another list to try and keep up to date > (alphabetized, of course). You're probably better off just asking > who's around whenever you're on. On the other hand, a lot of people, especially the people who do use IRC frequently and are therefore most likely to be found there, keep the same IRC handle for a long time (I've had mine, bitdancer, since 1995 or so). So I think there would be utility in such a list even if the updates were spotty. -- R. David Murray If you like the work I do for Python, you can enable me to spend more time doing it by supporting me here: http://gittip.com/bitdancer ___ 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] core dev IRC nicks
On 29.08.2012 15:38, R. David Murray wrote: On Tue, 28 Aug 2012 23:21:15 -0500, Brian Curtin wrote: On Tue, Aug 28, 2012 at 10:58 PM, Chris Jerdonek wrote: > Is there a list somewhere of the IRC nicks of the core developers that > use IRC (and who wish to be listed) alongside their real names? If > there is no such list, has there ever been discussion on python-dev of > creating such a list? I'm sure we could make one, but it's probably of limited utility since not many people are on IRC, and those who are come and go throughout the day, throughout the month, year, etc. It'd just end up being another list to try and keep up to date (alphabetized, of course). You're probably better off just asking who's around whenever you're on. On the other hand, a lot of people, especially the people who do use IRC frequently and are therefore most likely to be found there, keep the same IRC handle for a long time (I've had mine, bitdancer, since 1995 or so). So I think there would be utility in such a list even if the updates were spotty. But so far I've not seen a core developer without the real name field set to their, well, real name, so it's not quite as hard to find out who is who anyway. Georg ___ 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] core dev IRC nicks
On Wed, 29 Aug 2012 22:50:25 +0200 Georg Brandl wrote: > On 29.08.2012 15:38, R. David Murray wrote: > > On Tue, 28 Aug 2012 23:21:15 -0500, Brian Curtin wrote: > >> On Tue, Aug 28, 2012 at 10:58 PM, Chris Jerdonek > >> wrote: > >> > Is there a list somewhere of the IRC nicks of the core developers that > >> > use IRC (and who wish to be listed) alongside their real names? If > >> > there is no such list, has there ever been discussion on python-dev of > >> > creating such a list? > >> > >> I'm sure we could make one, but it's probably of limited utility since > >> not many people are on IRC, and those who are come and go throughout > >> the day, throughout the month, year, etc. > >> > >> It'd just end up being another list to try and keep up to date > >> (alphabetized, of course). You're probably better off just asking > >> who's around whenever you're on. > > > > On the other hand, a lot of people, especially the people who do use IRC > > frequently and are therefore most likely to be found there, keep the same > > IRC handle for a long time (I've had mine, bitdancer, since 1995 or so). > > So I think there would be utility in such a list even if the updates > > were spotty. > > But so far I've not seen a core developer without the real name field set > to their, well, real name, so it's not quite as hard to find out who is > who anyway. And there's probably an entertainment value to it. (I still wonder who "Alex_Gaynor" is, though) cheers Antoine. -- Software development and contracting: http://pro.pitrou.net ___ 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] Py_buffer.obj documentation
I am trying to reconcile this section in 3.3 documentation: """ void *obj A new reference to the exporting object. The reference is owned by the consumer and automatically decremented and set to NULL by PyBuffer_Release(). The field is the equivalent of the return value of any standard C-API function. As a special case, for temporary buffers that are wrapped by PyMemoryView_FromBuffer() or PyBuffer_FillInfo() this field is NULL. In general, exporting objects MUST NOT use this scheme. """ -- http://docs.python.org/dev/c-api/buffer.html#Py_buffer.obj with the following comment in the code (Objects/memoryobject.c:762): /* info->obj is either NULL or a borrowed reference. This reference should not be decremented in PyBuffer_Release(). */ I have not studied the code yet, but given the history of bugs in this area the code may not have the most authoritative answer. In any case, either the comment or the ReST section should be corrected. ___ 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] Py_buffer.obj documentation
On 29/08/2012 22:28, Alexander Belopolsky wrote: I am trying to reconcile this section in 3.3 documentation: """ void *obj A new reference to the exporting object. The reference is owned by the consumer and automatically decremented and set to NULL by PyBuffer_Release(). with the following comment in the code (Objects/memoryobject.c:762): /* info->obj is either NULL or a borrowed reference. This reference should not be decremented in PyBuffer_Release(). */ I've studied this code in the interests of reproducing something similar for Jython. The comment is in the context of PyMemoryView_FromBuffer(Py_buffer *info), at a point where the whole info struct is being copied to mbuf->master, then the code sets mbuf->master.obj = NULL. I think the comment means that the caller, which is in the role of consumer to the original exporter, owns the info struct and therefore the reference info.obj. That caller will eventually call PyBuffer_Release(info), which will result in a DECREF(obj) matching the INCREF(obj) that happened during bf_getbuffer(info). In this sense obj is a borrowed reference as far as the memoryview is concerned. mbuf->master must not also keep a reference, or it risks making a second call to DECREF(obj). Jeff Allen ___ 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
