> Perhaps 2.2 should deprecate direct use of strop noisily -- warn when > imported, except when imported by string.py. (No idea how you'd > implement that, I'm just spouting off.) Then it could go away in 2.3. I have had the necessary mods sitting in my directory for months (it was one of my first tests for using the warnings module), but decided against checking it in because I found there's quite a bit of code that triggered the warnings. Maybe I should check it in into 2.2a0, so developers can get used to it. > I don't think there's anything particularly controversial about 'strop' > going away after one release with a deprecation warning -- it's not > 'string', after all! (Ie. imported by every single scrap of Python code > ever written before string methods came along, and by quite a lot since > then.) Agreed. --Guido van Rossum (home page: http://www.python.org/~guido/)
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