On 03/13/2011 06:49 AM, Georg Brandl wrote: > On 12.03.2011 17:09, Eric Smith wrote: >> On 03/12/2011 10:55 AM, Éric Araujo wrote: >>>> I have a deprecation warning that I need to make an error in 3.4. >>> >>> A neat trick to remember to do those changes is using a test that fails >>> if something does not raise a DeprecationWarning if sys.version_info[:2] >>> == (3, 3), or an error if sys.version_info[:3] == (3, 4). You write >>> those tests once and let “make test” remind you as soon as the Python >>> version changes. >> >> I like the idea, but it seems a little hostile to the person who >> actually changes the version number! > > If it helps to remember these things (usually deprecations) that we've often > forgotten in the past, I don't mind being the one to innocently break the > buildbots by increasing the version number. Are you volunteering to change all of the PendingDeprecationWarnings to DeprecationWarnings and DeprecationWarnings to errors of some sort? It might be a big job. I'm just trying to figure out what the mechanics would be. Eric.
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