Re: [Python-Dev] PEP 338 issue finalisation (was Re: 2.5 PEP)

2006-02-17 Thread Nick Coghlan
Guido van Rossum wrote: > [Hey, I thought I sent that just to you. Is python-dev really > interested in this?] Force of habit on my part - I saw the python-dev header and automatically dropped "pyd" into the To: field of the reply. Given Paul's contribution on the get_data front, it turned out t

Re: [Python-Dev] PEP 338 issue finalisation (was Re: 2.5 PEP)

2006-02-17 Thread Guido van Rossum
On 2/16/06, Paul Moore <[EMAIL PROTECTED]> wrote: > On 2/16/06, Guido van Rossum <[EMAIL PROTECTED]> wrote: > > On 2/16/06, Nick Coghlan <[EMAIL PROTECTED]> wrote: > > > > The PEP itself requests that a string be returned from get_data(), but > > > doesn't > > > require that the file be opened in

Re: [Python-Dev] PEP 338 issue finalisation (was Re: 2.5 PEP)

2006-02-16 Thread Paul Moore
On 2/16/06, Guido van Rossum <[EMAIL PROTECTED]> wrote: > On 2/16/06, Nick Coghlan <[EMAIL PROTECTED]> wrote: > > The PEP itself requests that a string be returned from get_data(), but > > doesn't > > require that the file be opened in text mode. Perhaps the PEP 302 emulation > > should use binar

Re: [Python-Dev] PEP 338 issue finalisation (was Re: 2.5 PEP)

2006-02-16 Thread Guido van Rossum
On 2/16/06, Nick Coghlan <[EMAIL PROTECTED]> wrote: > Guido van Rossum wrote: > > Do you have unit tests for everything? I believe I fixed a bug in the > > code that reads a bytecode file (it wasn't skipping the timestamp). [Hey, I thought I sent that just to you. Is python-dev really interested i

[Python-Dev] PEP 338 issue finalisation (was Re: 2.5 PEP)

2006-02-16 Thread Nick Coghlan
Guido van Rossum wrote: > On 2/15/06, Nick Coghlan <[EMAIL PROTECTED]> wrote: >> PEP 338 is pretty much ready to go, too - just waiting on Guido's review and >> pronouncement on the specific API used in the latest update (his last PEP >> parade said he was OK with the general concept, but I only po