glyph at divmod.com wrote: >>> python -U is a failure for obvious reasons and a >>> __future__ import is clearly better. >> I disagree. > > I am surprised that you do, since I thought that Chris's conclusion was > pretty obvious. Python -U doesn't work, even on the standard library. Sure, it doesn't work. That doesn't mean it's "a failure". It just hasn't been completed yet. > A __future__ import would allow these behaviors to be upgraded module-by-module. > Right now, all -U provides is an option that can't be used on any realistically > sized program, so I don't see what the utility is. People can use it to improve the Unicode support in the Python standard library. When they find that something doesn't work, they can study the problem, and ponder possible solutions. Then, they can contribute patches. -U has worked fine for me in the past, I contributed various patches to make it work better. It hasn't failed for me at all. Regards, Martin
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