[Python-Dev] [PEP 437] A DSL for specifying signatures, annotations and argument converters

2013-03-16 Thread Stefan Krah
This PEP hasn't been announced yet, so here's a short notice for all people
(like myself) who are not at PyCon. This is the counter proposal for the
argument parsing DSL from PEP 436:

   http://www.python.org/dev/peps/pep-0437/


Both PEPs were discussed at PyCon.  The state of affairs is that a
compromise is being worked upon and will be published by Larry in
a revised PEP.



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] [Python-checkins] cpython (merge default -> default): Merge heads default.

2013-03-16 Thread Ezio Melotti
Hi,

On Sat, Mar 16, 2013 at 10:08 PM, terry.reedy
 wrote:
> http://hg.python.org/cpython/rev/9a2f4418e65a
> changeset:   82699:9a2f4418e65a
> parent:  82691:0a15a58ac4a1
> parent:  82695:533a60251b9d
> user:Terry Jan Reedy 
> date:Sat Mar 16 16:08:12 2013 -0400
> summary:
>   Merge heads default.
>
> files:
>   Doc/library/functions.rst |  4 ++--
>   1 files changed, 2 insertions(+), 2 deletions(-)
>

You forgot a couple of merges here.
If you look at the graph at
http://hg.python.org/cpython/graph/9a2f4418e65a you will see that all
the heads in the individual branches got merged, but then you forgot
to merge 3.2 -> 3.3 -> default (i.e. steps 5 and 6 of
http://bugs.python.org/issue14468#msg184130).  Serhiy fixed that
shortly after: http://hg.python.org/cpython/graph/5da005db8166
At least now that the worst case scenario that doesn't really happen
often™[0] happened I can point to some actual graphs that will
hopefully clarify why all these merges are necessary :)

Best Regards,
Ezio Melotti

[0]: http://bugs.python.org/issue14468#msg184140
___
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] [Python-checkins] cpython (merge default -> default): Merge heads default.

2013-03-16 Thread Ezio Melotti
On Sat, Mar 16, 2013 at 11:48 PM, Terry Reedy  wrote:
> The FAQ says "...  using hg merge 3.3 as usual." Serhiy's commit message
> said 'Null merge', which to me is not 'as usual', as there are extra steps
> given in the FAQ above. So, do he really do a 'null merge' and is that the
> right thing to do in this situation?
>

It's probably just a matter of terminology.  I assume he did a "usual
merge" (i.e. "hg merge 3.2; hg ci -m '...';") and call it "null merge"
because there was no code that changed.  I prefer to use the term
"null merge" when I explicitly revert the code before committing, and
in this case I would have used "Merge with 3.x.".

FWIW I might add http://bugs.python.org/issue15917 at some point, to
prevent these situations.

Best Regards,
Ezio Melotti


> I have no doubt the the extra merges are needed ;-).
___
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] About issue 6560

2013-03-16 Thread Glyph
On Mar 14, 2013, at 3:48 PM, Martin v. Löwis  wrote:

> Am 14.03.13 15:15, schrieb Ani Sinha:
>> I was looking into a mechanism to get the aux fields from recvmsg() in
>> python and I came across this issue. Looks like this feature was added
>> in python 3.3. Is there any reason why this feature was not added for
>> python 2.7?
> 
> Most certainly: Python 2.7 (and thus Python 2) is feature-frozen; no
> new features can be added to it. People wanting new features need to
> port to Python 3.


Or you can use Twisted: 


That module ought to have no dependencies outside of Twisted.

We only use it for passing file descriptors between processes, but I believe it 
should be able to deal with whatever other types of auxiliary data that you 
need from recvmsg; if not, please file a bug (at ).

-glyph

___
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