I understand now that I simply don't have enough clue about the implementation to even try to be involved with this. Unless it makes sense to have a PEP that doesn't touch the implementation at all (doubtful, IMHO), I'll take back my offer to write one. I still think it's an important issue, but it's simply beyond what I can deal with. To solve the issues on MacOS X, maybe it's enough to hack the Carbon version of stdio so it can handle unix text files. That way we can simply settle for unix line ending if sharing code between BSD Python and Carbon Python is desired. At the same time this would allow using CVS under Darwin for MacPython sources, which is something I look forward to... Just
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