> Something I forgot last time around: as soon as we have > Python source code encodings, disabling Unicode will no > longer be "easy". > > If you still want to proceed with this, then please add the > test for ASCII-compatibility, since otherwise code can easily > become non-portable between Python Unicode/non-Unicode builds > anymore without anyone noticing. IMO a simpler solution would be to check for en encoding cookie and complain when Unicode is not enabled. I am not interested in making everything work perfectly with Unicode disabled -- that's not possible any more. I *am* interested in being able to run as much of the test suite as makes sense with Unicode disabled. This mostly means that code that contains tests of the form "is this object a Unicode string?" should get an answer "no" rather than an exception. I am not interested in making code that uses unicode() somehow work without it. --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