[issue20074] open() of read-write non-seekable streams broken

2020-04-10 Thread pavlix
pavlix added the comment: > A non-seekable read/write stream doesn't really make sense (think about it). How does it help the issue to ask the reporter to "think" when the have already provided an easily reproducable use case? > What purpose does that constraint serve

[issue20074] open() of read-write non-seekable streams broken

2020-04-10 Thread pavlix
pavlix added the comment: Okay, let me help the situation a bit. The “workaround” of using `buffering=0` works perfect with `rb+` and `wb+` and I'm pretty sure I used this in the past. I don't know how well this is documented. I would usually need to disable buffering for any