[Python-Dev] unicode_string future, str -> basestring, fix or feature
Serhiy Storchaka
storchaka at gmail.com
Sun Mar 2 22:23:55 CET 2014
More information about the Python-Dev mailing list
Sun Mar 2 22:23:55 CET 2014
- Previous message: [Python-Dev] unicode_string future, str -> basestring, fix or feature
- Next message: [Python-Dev] unicode_string future, str -> basestring, fix or feature
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
02.03.14 22:01, Terry Reedy написав(ла): > Is this a programmer error for passing unicode instead of string, or a > library error for not accepting unicode? > Is changing 'isinstance(x, str)' in the library (with whatever other > changes are needed) a bugfix to be pushed or a prohibited API expansion? Patches which add support for unicode strings were accepted for one issues (e.g. http://bugs.python.org/issue19099) and rejected for other issues (e.g. http://bugs.python.org/issue20014 and http://bugs.python.org/issue20015). Some issues (e.g. http://bugs.python.org/issue18695) hang in undefined state.
- Previous message: [Python-Dev] unicode_string future, str -> basestring, fix or feature
- Next message: [Python-Dev] unicode_string future, str -> basestring, fix or feature
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-Dev mailing list