21.06.2011 19:30, Dan Stromberg <[email protected]>: > On Tue, Jun 21, 2011 at 12:15 AM, Chris Torek <[email protected]> wrote: > > I have an idea I think would be useful, although exactly how useful > > I am not sure, and just how to implement it is an even bigger > > question. > > > > Suppose that we had a way of finding which exceptions are > > (potentially) raised by all the built-in Python functions. (For > > now, this would have to be read from a file, or built in to pylint > > / astng, or something like that, which is not a very nice way to > > get started, but so it goes.) > > I agree that this would be useful. It might be worth mentioning on > python-ideas as well. I've not done much with Java but when I saw > this feature in Java, I wished Python had it.
Well you have obviously not done much with Java. Checked exceptions are
one of *the* most annoying ”features” of that language. It makes
generic programming hard to impossible in some cases. There are many
built in functions that can raise virtually *any* exception. `map` and
`filter` for example. Or the `next()` function/method. Even `str()` or
`int()`!
Ciao,
Marc 'BlackJack' Rintsch
--
“Programs must be written for people to read,
and only incidentally for machines to execute.”
-- Abelson & Sussman, SICP (preface to the first edition)
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Python-Projects mailing list [email protected] http://lists.logilab.org/mailman/listinfo/python-projects
