Re: [Python-3000] [Python-Dev] Python 3000 Status Update (Long!)

2007-06-28 Thread Nick Coghlan
Greg Ewing wrote: > Russell E. Owen wrote: >> I would personally be happy lose set comprehensions and just use >> generator expressions for all comprehension-like tasks. > > One advantage of the comprehension syntaxes is that the > body can be inlined instead of relegated to a lambda, > saving th

Re: [Python-3000] StringIO/BytesIO in io.py doesn't over-seek properly

2007-06-28 Thread Alexandre Vassalotti
Can someone, other than Guido, review my patch? He is in vacation right now, so he probably won't have the time to review and submit it until August. Thanks, -- Alexandre On 6/25/07, Alexandre Vassalotti <[EMAIL PROTECTED]> wrote: > On 6/23/07, Guido van Rossum <[EMAIL PROTECTED]> wrote: > > On 6

Re: [Python-3000] pimp; restructuring the standard library

2007-06-28 Thread Phillip J. Eby
At 04:59 PM 6/28/2007 +0100, tav wrote: >* Abandoning of unit tests and replacing with full doctest coverage in >the style perfected by Jim Fulton and PJE. Integration with py.test. I believe that the origination credit for this rightly falls to Tim Peters. (I just copied Jim, myself.) Meanwhil

Re: [Python-3000] pimp; restructuring the standard library

2007-06-28 Thread tav
> Indeed, I'm also wary of breaking backward compatibility of unittest > or doctest in Python 3.0, because that will make it even harder to > port code over. How will 2.x users run their existing test suites to > verify their code has been ported correctly, if they can't keep using > unittest? As

Re: [Python-3000] pimp; restructuring the standard library

2007-06-28 Thread Brett Cannon
On 6/28/07, tav <[EMAIL PROTECTED]> wrote: > > Indeed, I'm also wary of breaking backward compatibility of unittest > > or doctest in Python 3.0, because that will make it even harder to > > port code over. How will 2.x users run their existing test suites to > > verify their code has been ported

[Python-3000] Py3k doesn't understand octal literals (on Windows)

2007-06-28 Thread Thomas Heller
In a break from real work, I wanted to play a little with 3.0. Did svn update, and built on Windows. Unfortunately, the resulting Python does not understand the new octal literals like 0o777, so importing 'os' fails: 'import site' failed; use -v for traceback Python 3.0x (p3yk:55071M, May 2 20

Re: [Python-3000] Py3k doesn't understand octal literals (on Windows)

2007-06-28 Thread Thomas Heller
Thomas Heller schrieb: > In a break from real work, I wanted to play a little with 3.0. Did svn > update, and built on Windows. > Unfortunately, the resulting Python does not understand the new octal > literals like 0o777, so > importing 'os' fails: > > 'import site' failed; use -v for tracebac

[Python-3000] doctests vs. unittests (was Re: pimp; restructuring the standard library)

2007-06-28 Thread Chris McDonough
On Jun 28, 2007, at 12:41 PM, Phillip J. Eby wrote: > At 04:59 PM 6/28/2007 +0100, tav wrote: >> * Abandoning of unit tests and replacing with full doctest >> coverage in >> the style perfected by Jim Fulton and PJE. Integration with py.test. > > I believe that the origination credit for this ri

Re: [Python-3000] doctests vs. unittests (was Re: pimp; restructuring the standard library)

2007-06-28 Thread Fred L. Drake, Jr.
On Thursday 28 June 2007, Chris McDonough wrote: > a) If one of your fixture calls or an assertion fails for some > reason, the rest of the test > trips over itself trying to complete, usually without success > because an invariant > hasn't been met, and you need to scroll through a bu

Re: [Python-3000] doctests vs. unittests (was Re: pimp; restructuring the standard library)

2007-06-28 Thread Phillip J. Eby
At 04:04 PM 6/28/2007 -0400, Chris McDonough wrote: >a) If one of your fixture calls or an assertion fails for some >reason, the rest of the test > trips over itself trying to complete, usually without success >because an invariant > hasn't been met, and you need to scroll through a bunch o

Re: [Python-3000] [Python-Dev] Python 3000 Status Update (Long!)

2007-06-28 Thread Greg Ewing
Nick Coghlan wrote: > There is no function call per loop even when using a > generator expression - a generator function is implicit defined, and > then called once to instantiate the generator. You're right -- I must have been half-thinking of map() at the time. Resuming the generator ought to

Re: [Python-3000] doctests vs. unittests (was Re: pimp; restructuring the standard library)

2007-06-28 Thread Barry Warsaw
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Jun 28, 2007, at 4:04 PM, Chris McDonough wrote: > I've historically not been a huge fan of doctests because (these > things may have changed since last I used doctest in anger): I used to think the same thing, but I've gotten the doctest religi

Re: [Python-3000] doctests vs. unittests (was Re: pimp; restructuring the standard library)

2007-06-28 Thread Chris McDonough
On Jun 28, 2007, at 11:46 PM, Barry Warsaw wrote: > The thing that convinced me was the realization (assisted by my > colleagues) that doctests are first and foremost documentation. > They are testable documentation sure, but the unit tests are > secondary. There's no question that for thi

Re: [Python-3000] doctests vs. unittests (was Re: pimp; restructuring the standard library)

2007-06-28 Thread Mark Hammond
Barry writes: > On Jun 28, 2007, at 4:04 PM, Chris McDonough wrote: > > > I've historically not been a huge fan of doctests because (these > > things may have changed since last I used doctest in anger): > > I used to think the same thing, but I've gotten the doctest > religion. I'm using them al