Martin v. Löwis wrote:
>
>> Not if it includes code that looks like this:
>>
>> if type(response) in (str, unicode): .....
>>
>> and it's really true that "[a]nything having to do with the
>> str->bytes/unicode->str move is so far off-limits" to the upgrade tool.
>
> Depends on what the purpose of the test is. If it tests for
> "is response text", then 2to3 will work just fine on it, converting
> it to
>
> if type(response) in (str, str):
Then I'm taking him too literally, when he writes that the tool won't
touch *anything* that has to do with the str->bytes/unicode->str move (I
assumed that meant it wouldn't touch "unicode" in the snippet I gave
above), right?
Will the tool also make the following work correctly?
if type(s) is str: s = unicode(s, 'utf-8')
--
Bob Kline
http://www.rksystems.com
mailto:[EMAIL PROTECTED]
_______________________________________________
Python-Dev mailing list
[email protected]
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
