All,
I have to request your continued patience. Several of you have sent me
code or ideas to review. I *will* get to it, probably early next week;
but recovery from PyCon, first physical, then from the backlog at
work, has made it necessary to prioritize things. While I have minutes
here and there
On 12/18/06, Guido van Rossum <[EMAIL PROTECTED]> wrote:
> I think a reasonable solution here is to make the C version an
> optional implementation detail of the Python version, such as was done
> for the heapq module already (the C version is _heapq and
> automatically imported by heapq.py if it e
On 2/28/07, Daniel Stutzbach <[EMAIL PROTECTED]> wrote:
> What should Buffered I/O .write() do for a non-blocking object?
> It seems like the .write() should write as much as it can to the Raw
> I/O object and buffer the rest, but then how do we tell the Buffered
> I/O object to "write more data f
"Daniel Stutzbach" <[EMAIL PROTECTED]> wrote:
[snip]
> The goal of supporting non-blocking file-like objects is to be able to
> use select() with buffered I/O objects (and other things like a
> compressed socket stream).
You can already pass sockets, files, and pipes to select (on linux, bsd,
etc
I spent my sprint time cleaning up exceptions for Py3K and Guido
suggested I run some things by the group to make sure they don't make
transitioning from 2.6 too difficult. After adding the proper
restrictions in terms of what can and cannot be raised or caught, I
began cleaning up BaseException's
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
On 2/28/07, Daniel Stutzbach <[EMAIL PROTECTED]> wrote:
> What should Buffered I/O .write() do for a non-blocking object?
>
> It seems like the .write() should write as much as it can to the Raw
> I/O object and buffer the rest, but then how do we tell the Buffered
> I/O object to "write more data
On 2/27/07, Travis E. Oliphant <[EMAIL PROTECTED]> wrote:
> Rationale
(This was a good section; thank you.)
> 5. There is no shape information provided for the memory. But,
>several array-like Python types could make use of a standard
>way to describe the shape-interpretati
What should Buffered I/O .write() do for a non-blocking object?
It seems like the .write() should write as much as it can to the Raw
I/O object and buffer the rest, but then how do we tell the Buffered
I/O object to "write more data from the buffer but still don't block"?
Along the same lines, fo
