comed.
We've published it on Google Docs here:
http://docs.google.com/Doc?id=dfksfvqd_1cn5g5m
What follows is a plaintext version.
Thanks,
Mike.
PEP: XXX
Title: New IO
Version:
Last-Modified:
Authors: Daniel Stutzbach, Mike Verdone
Status: Draft
Type:
Created: 26-Feb-2007
Rationale and Go
Hi Pete,
These look very good. My comments to your comments below,
> 1. The early python implementation does not allow "reusing" an argument
> either by index or by keyword name. The PEP has not defined this behavior. I
> think it is important to be allowed to reuse any of the argument objects
>
Hi Talin,
Some more thoughts...
> Here's my primary issue with this: I wanted a way to enable strictness
> on an application-wide level, without having to go and individually
> revise the many (typically hundreds) of individual calls to the string
> formatting function.
>
> A typical example of w
The current algorithm for non-blocking writes is as follows:
When write is called check if the buffer is bigger than buffer_size.
If it is attempt to pre-flush the buffer. If we can't pre-flush, raise
BlockingIO error. Else, copy the new write data into the buffer
(flushed or not) and if we're big
