Cody Maloney

Planning to close this issue once the two outstanding PRs are closed. There are more improvements I think are possible, but they're large enough scoped individual changes they should likely...

For the startup "read 4 times" case, I looked a bit and it's really complex to unwind for likely minimal performance (OS filecache saves quite a bit). It's a combination...

Thanks for your help in reviewing, helping me learn CPython, and getting the patches landed; sorry there were quite so many follow up patches, but think we got there :)....

For these is there any way to differentiating/expose the difference in `.write()` behavior between "Raw I/O" (ex. `io.FileIO`) vs. high level I/O (`BufferedIO` and `TextIO`)? For "Raw I/O" if the...

Given this has been implemented and backported can the issue be closed? (cc: @ambv, @serhiy-storchaka )

I have made the requested changes; please review again also: Could this get the "skip news" label? From my perspective not a python user visible behavior change

Yea, I think I've addressed all of @gpshead's review comments, I haven't clicked 'resolved conversation' though to keep the review visible for context

Sounds good to me. Think i have all the bits to try that raspbian locally, need to figure out what its syscall name for fstat looks like

Currently working on / current draft UI (Button to "load" the current issue, dropdown for recent issues by the user)

Cases including classes which implement `__bytes__()` that return both valid (ex. `bytes`) and non-valid (ex. `str`) values are tested in `test_long`, `test_from_bytes` so I don't think any critical behavior changes...