Re: [Python-Dev] Reject bytearray filename in Python 3.2

2010-04-21 Thread Victor Stinner
Le jeudi 22 avril 2010 00:21:02, vous avez écrit : > Victor Stinner wrote: > > I will be very sad if someone ask me to keep bytearray filename support > > in 3.2 because I opened a lot of issues about surrogates and I would make > > my work more diffcult :-( > > I don't have an opinion one way or

Re: [Python-Dev] Reject bytearray filename in Python 3.2

2010-04-21 Thread Nick Coghlan
Victor Stinner wrote: > I will be very sad if someone ask me to keep bytearray filename support in > 3.2 > because I opened a lot of issues about surrogates and I would make my work > more diffcult :-( I don't have an opinion one way or the other regarding bytearray, but even if you deprecated

Re: [Python-Dev] Small suggestion re help(Exception)

2010-04-21 Thread Nick Coghlan
Rob Cliffe wrote: > Yes, exactly like that. > I wasn't aware of __subclasses__ (it doesn't appear in > dir(ArithmeticError), > for example) Slight tangent: dir() usually includes class attributes (e.g. "set(dir(1)) >= set(dir(int))"), but to prevent weirdness that particular feature is omitted for

[Python-Dev] Reject bytearray filename in Python 3.2

2010-04-21 Thread Victor Stinner
Hi, About my work on unicode surrogates, I would like to reject bytearray filename, especially in the PyUnicode_FSConverter function. As explained in issue #8485, support bytearray requires to test the result type, acquire/release a lock, the API is more complex, etc. I don't know real world u

Re: [Python-Dev] PEP 328, relative imports and Python 2.7

2010-04-21 Thread Barry Warsaw
On Apr 21, 2010, at 02:56 PM, Mark Dickinson wrote: >On Wed, Apr 21, 2010 at 2:40 PM, Barry Warsaw wrote: >> While talking about Python 2.6 -> 2.7 transitions, the subject of relative >> and >> absolute imports has come up.  PEP 328 states that absolute imports will be >> enabled by default in P

Re: [Python-Dev] PEP 328, relative imports and Python 2.7

2010-04-21 Thread Brett Cannon
On Wed, Apr 21, 2010 at 06:58, Mark Dickinson wrote: > On Wed, Apr 21, 2010 at 2:56 PM, Mark Dickinson > wrote: > > On Wed, Apr 21, 2010 at 2:40 PM, Barry Warsaw wrote: > >> While talking about Python 2.6 -> 2.7 transitions, the subject of > relative and > >> absolute imports has come up. PEP

Re: [Python-Dev] Small suggestion re help(Exception)

2010-04-21 Thread Rob Cliffe
- Original Message - From: "Aurélien Campeas" To: "Rob Cliffe" Sent: Wednesday, April 21, 2010 5:25 PM Subject: Re: [Python-Dev] Small suggestion re help(Exception) > like in > ArithmeticError.__subclasses__() > [, 'exceptions.OverflowError'>, ] > > ? Yes, exactly like that. I w

Re: [Python-Dev] argparse ambiguity handling

2010-04-21 Thread Steven Bethard
On Wed, Apr 21, 2010 at 2:14 AM, Jon Ribbens wrote: > On Wed, Apr 21, 2010 at 03:53:16AM -0400, Eric Smith wrote: >> I agree the new behavior is desirable. And I also think it should be the >> default, although I feel less strongly about that. >> >> But since this behavior seems to be an accident

Re: [Python-Dev] Small suggestion re help(Exception)

2010-04-21 Thread Michael Foord
On 21/04/2010 18:17, Rob Cliffe wrote: help() on an Exception class lists the method resolution order (effectively the inheritance hierarchy). E.g. help(ArithmeticError) displays inter alia: Method resolution order: ArithmeticError StandardError Exception BaseException __buil

[Python-Dev] Small suggestion re help(Exception)

2010-04-21 Thread Rob Cliffe
help() on an Exception class lists the method resolution order (effectively the inheritance hierarchy). E.g. help(ArithmeticError) displays inter alia: Method resolution order: ArithmeticError StandardError Exception BaseException __builtin__.object Would it be possible for i

Re: [Python-Dev] Email addresses for new committers for python-committers

2010-04-21 Thread Giampaolo Rodolà
I'm already subscribed as "g.rod...@gmail.com" and I'm able to receive messages from the list. 2010/4/20 Brett Cannon : > If you are a committer and are NOT subscribed to the python-committers > mailing list (I believe this at least includes Giampaolo, JP, and Brian), > then please either reply to

[Python-Dev] jean-claude elias

2010-04-21 Thread Robert Hancock
http://www.aricciafestaecultura.it/home.php ___ 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] PEP 328, relative imports and Python 2.7

2010-04-21 Thread Mark Dickinson
On Wed, Apr 21, 2010 at 2:56 PM, Mark Dickinson wrote: > On Wed, Apr 21, 2010 at 2:40 PM, Barry Warsaw wrote: >> While talking about Python 2.6 -> 2.7 transitions, the subject of relative >> and >> absolute imports has come up.  PEP 328 states that absolute imports will be >> enabled by default

Re: [Python-Dev] PEP 328, relative imports and Python 2.7

2010-04-21 Thread Mark Dickinson
On Wed, Apr 21, 2010 at 2:40 PM, Barry Warsaw wrote: > While talking about Python 2.6 -> 2.7 transitions, the subject of relative and > absolute imports has come up.  PEP 328 states that absolute imports will be > enabled by default in Python 2.7, however I cannot verify that this has > actually h

Re: [Python-Dev] Python 2.7b1 and argparse's version action

2010-04-21 Thread Nick Coghlan
Tobias Herp wrote: > > What /is/ this ambiguity of the "version=" argument? There is none! > > Do it the way optparse does it, and all is fine! All is not fine. How do I add a "-V" shortcut that is equivalent to "--version" as part of an optparse program? (That's a real question, I honestly hav

[Python-Dev] PEP 328, relative imports and Python 2.7

2010-04-21 Thread Barry Warsaw
While talking about Python 2.6 -> 2.7 transitions, the subject of relative and absolute imports has come up. PEP 328 states that absolute imports will be enabled by default in Python 2.7, however I cannot verify that this has actually happened. * Misc/NEWS doesn't mention it * What's New in Pytho

Re: [Python-Dev] argparse ambiguity handling

2010-04-21 Thread Jon Ribbens
On Wed, Apr 21, 2010 at 03:53:16AM -0400, Eric Smith wrote: > I agree the new behavior is desirable. And I also think it should be the > default, although I feel less strongly about that. > > But since this behavior seems to be an accident of the implementation > (based on Steve's comment above

Re: [Python-Dev] argparse ambiguity handling

2010-04-21 Thread Eric Smith
Cameron Simpson wrote: On 20Apr2010 15:27, Neal Becker wrote: | Steven Bethard wrote: | | > On Tue, Apr 20, 2010 at 11:55 AM, Neal Becker wrote: | >> I've noticed argparse ambiguity handling has changed a bit over last few | >> revisions. | >> | >> I have cases where 1 valid input is a prefix