On Tue, Apr 15, 2008 at 3:27 PM, Greg Ewing <[EMAIL PROTECTED]> wrote: > 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.
Well, that's your problem. That's not what EnvironmentErrors are for. > > 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. Right. -- --Guido van Rossum (home page: http://www.python.org/~guido/) _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
