Matthew Wilkes wrote: > > On 1 Jun 2009, at 17:50, Dino Viehland wrote: > >> I’m just a little surprised by this - Is there a reason why syntax >> warnings are special and untrappable via warnings.warn? > > Why should this work? From the docs... "Python programmers issue > warnings by calling the warn() function defined in this module. (C > programmers use PyErr_WarnEx; see Exception Handling for details)." > > Check out the warnings.catch_warnings context manager, but if you have > any further questions please direct them to the normal Python mailing > list, this is for development _of_ Python only. Dino is developing Python - he's one of the core developers of IronPython and I suspect he is asking whether this is intentional, and IronPython should implement the same behaviour, or whether it is a bug. Michael > > Matthew > _______________________________________________ > Python-Dev mailing list > Python-Dev at python.org > http://mail.python.org/mailman/listinfo/python-dev > Unsubscribe: > http://mail.python.org/mailman/options/python-dev/fuzzyman%40voidspace.org.uk > -- http://www.ironpythoninaction.com/ http://www.voidspace.org.uk/blog
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