Fredrik Lundh wrote: > Just wrote: > > > > why not fix the compiler instead? > > > > > > Exactly. That is where the correct fix should go. The compile can/should > > > recognize all types of newlines as the NEWLINE token. > > > > The same goes for file objects in text mode... > > probably -- but changing can break stuff (in theory, at least), and > may require a PEP. changing the compiler is more of a bugfix, really... But if we only fix the compiler, we'll get complaints that other things don't work, eg. bogus tracebacks due to a non-fixed linecache.py, broken IDE's, etc. Btw. I can't seem to think of any examples that would break after such a change. I mean, who would depend on a \n text file with embedded \r's? 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