On Thu, Jun 26, 2008 at 9:01 AM, Jean-Paul Calderone <exarkun at divmod.com> wrote: > On Fri, 27 Jun 2008 01:52:18 +1000, Nick Coghlan <ncoghlan at gmail.com> wrote: >> >> Jean-Paul Calderone wrote: >>> >>> I don't particularly care about the details, I just want some public >>> API for this. Making warn_explicit public seems better to me, since >>> it was already there in previous versions of Python, and it lets you >>> completely ignore both the filters list and the global registry, but >>> if others would rather make the filters and global registry a part of >>> the public API, that's fine by me as well. >> >> Why do you say warn_explicit isn't public? It's in both the 2.5 and 2.6 >> API docs for the warnings module. > > Brett told me it was private (on this list several weeks or a month or so > ago). It's also no longer called in 2.6 by the C implementation of the > warning system. > I don't remember saying it is private, just that you can't replace the function in the module and expect everything to continue to work properly like you can with showwarning(). -Brett
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