Guido van Rossum wrote: > No, that's some kind of parsing error. EnvironmentError doesn't > concern itself with the contents of files. Often I raise EnvironmentErrors of my own to signal parsing errors. This makes it easy to wrap everything in a try-except that catches anything that's the user's fault rather than the program's. > But what operations raise EOFError? Surely you're not using > raw_input()? It's really only there for teaching. I'm fairly sure there are some others, although I can't point to them on the spur of the moment. However, thinking about it a bit more, anything that calls something that can raise EOFError should be catching it anyway, so an escaped EOFError represents a program bug. So it's probably okay. -- Greg
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