Guido van Rossum <guido <at> python.org> writes: > > However, the semantics of interleaving > reads and writes, with and without seek calls in between, should be > well-defined and correct/useful, so that it behaves the same > regardless of the buffer size. Yes, the goal is to have reasonably intuitive, and meaningful, semantics. > Ditto for the flush call currently implied by a seek -- if you can > satisfy the seek by moving where you are in the buffer without > flushing, that's fine IMO, but it should be well documented. That's also part of what I've tried to optimize. The documentation is currently in the limbs, though. Thanks! Antoine.
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4