Paul Moore wrote: > 2009/6/15 Terry Reedy <tjreedy at udel.edu>: >> Raymond Hettinger wrote: >> >>> P.S. If you switch to PendingDeprecationWarning, the example >>> in the docs should probably be switched to show the one valid >>> use case (passing in a prepackaged nest of context managers). >> It could even suggest that it only be used for this, since it may disappear, >> and that other uses should use the new syntax. That would give people the >> best chance of writing future-proof code when they can. > > And if the warning is *not* changed to a PendingDeprecationWarning, > the documentation could also note the necessary warnings call needed > to let the example code run warning-free. I think I like that option even better than downgrading the warning. I created http://bugs.python.org/issue6288 to make it clear to Benjamin when I have finished updating the docs. Cheers, Nick. -- Nick Coghlan | ncoghlan at gmail.com | Brisbane, Australia ---------------------------------------------------------------
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