Guido> I wonder if it would make sense to put a warning when people use
Guido> f.read(n) on a file opened in text mode? I think f.read(n) is an
Guido> almost sure sign that they're seeing the file as binary data.
Guido> However, f.read() or f.read(-1) is used to slurp in text as well,
Guido> so should not trigger the warning.
Guido> Opinions?
Pass this off to PyChecker?
I guess with the presence of PyChecker I'm getting a bit schizophrenic about
whether warnings go in the Python byte compiler or in PyChecker. It warns
about so many more things now than the compiler as it stands that it seems
to me to be the more natural place to stick new warnings.
Skip
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