Re: [Python-3000] Still get rid of the stat module?

2008-08-21 Thread Dirkjan Ochtman
Guido van Rossum wrote: Why? We could just deprecate it and rip it out in 3.1 or 3.2. In that case, not doing it for 3.0 seems just fine. Cheers, Dirkjan ___ Python-3000 mailing list Python-3000@python.org http://mail.python.org/mailman/listinfo/pyt

Re: [Python-3000] PEPs 3106 and 3119

2008-08-21 Thread Nick Coghlan
Guido van Rossum wrote: > 2008/8/21 Nick Coghlan <[EMAIL PROTECTED]>: >> Levi wrote: >>> Now, I understand that set doesn't return NotImplemented to avoid having >>> it's __cmp__ method called, but what I don't get is why it has a __cmp__ >>> method at all. I thought the entire point of set and co.

Re: [Python-3000] Still get rid of the stat module?

2008-08-21 Thread Guido van Rossum
On Thu, Aug 21, 2008 at 12:54 PM, Dirkjan Ochtman <[EMAIL PROTECTED]> wrote: > Brett Cannon wrote: >> >> So my question is whether it is still worth trying to remove the >> module, or just leave it be. > > Seeing this is the only chance in the coming 15 years to fix this, I'd say > fix it... Having

Re: [Python-3000] Still get rid of the stat module?

2008-08-21 Thread Dirkjan Ochtman
Brett Cannon wrote: So my question is whether it is still worth trying to remove the module, or just leave it be. Seeing this is the only chance in the coming 15 years to fix this, I'd say fix it... Having it around is pretty ugly, when the "real" stat() is actually in os. Cheers, Dirkjan

[Python-3000] Still get rid of the stat module?

2008-08-21 Thread Brett Cannon
PEP 3108 has the stat module slated for removal, but some snags have been hit and it makes me wonder if it is still worth it. The issue tracking all of this is http://bugs.python.org/issue2874 . First, it turns out a bunch of constants from the module are used all over the place. Those constants w

Re: [Python-3000] PEPs 3106 and 3119

2008-08-21 Thread Guido van Rossum
2008/8/21 Nick Coghlan <[EMAIL PROTECTED]>: > Levi wrote: >> Now, I understand that set doesn't return NotImplemented to avoid having >> it's __cmp__ method called, but what I don't get is why it has a __cmp__ >> method at all. I thought the entire point of set and co. using the rich >> comparison

Re: [Python-3000] issue 3187 and decoding filenames

2008-08-21 Thread Victor Stinner
Le Thursday 21 August 2008 15:30:22 Benjamin Peterson, vous avez écrit : > Issue 3187 is a case where os.listdir tries to decode filenames with > the default file system encoding, but failing that, simply returns the > unencoded bytestring. This was obviously ok in 2.x, but not so good in > py3k wh

[Python-3000] issue 3187 and decoding filenames

2008-08-21 Thread Benjamin Peterson
Issue 3187 is a case where os.listdir tries to decode filenames with the default file system encoding, but failing that, simply returns the unencoded bytestring. This was obviously ok in 2.x, but not so good in py3k where bytes are cleanly separated from unicode. Any comments on the issue are welc

Re: [Python-3000] PEPs 3106 and 3119

2008-08-21 Thread Nick Coghlan
Levi wrote: > Now, I understand that set doesn't return NotImplemented to avoid having > it's __cmp__ method called, but what I don't get is why it has a __cmp__ > method at all. I thought the entire point of set and co. using the rich > comparison operators is that Sets only define a partial order

Re: [Python-3000] io deadlock, use of RLock, issues 3618 & 3001 thoughts

2008-08-21 Thread Antoine Pitrou
Gregory P. Smith krypto.org> writes: > > http://bugs.python.org/issue3618 is a release blocker due to deadlock > in the io library. > > and the related C RLock implementation in [etc.] By the way, please note using an RLock will just solve the deadlock bug. It won't make the behaviour of write