According to the wxPython documentation on wx.OutputStream, the only
really usable method on this object is .write() (was .Write() in C++).
In the original wxWidgets documentation, wxOutputStream has a second
method, .LastWrite(), which would tell you how much data was actually
written, if, for example, one was sending a process created with
wx.Execute and wx.Process more data than its pipe could handle *now*.
According to the wxPython source (_streams.i), there isn't buffering
going on in the wxPython wrapped wx.OutputStream, but there also isn't a
usable .LastWrite() method to determine how much data was sent.
What would it take to get a usable .LastWrite() method?
- Josiah
Would you do it, or would you like a patch? Where is the documentation
so that I can update that too?
- Josiah
···
Robin Dunn <robin@alldunn.com> wrote:
Josiah Carlson wrote:
> According to the wxPython documentation on wx.OutputStream, the only
> really usable method on this object is .write() (was .Write() in C++).
> In the original wxWidgets documentation, wxOutputStream has a second
> method, .LastWrite(), which would tell you how much data was actually
> written, if, for example, one was sending a process created with
> wx.Execute and wx.Process more data than its pipe could handle *now*.
>
> According to the wxPython source (_streams.i), there isn't buffering
> going on in the wxPython wrapped wx.OutputStream, but there also isn't a
> usable .LastWrite() method to determine how much data was sent.
>
> What would it take to get a usable .LastWrite() method?
Just ask. 