OK, *that* sounds like an excellent reason to keep the Unicode disabled builds functional, and make sure they stay that way with a buildbot: to help make sure we're not accidentally running afoul of the implicit interoperability between str and unicode when backporting fixes from Python 3.

">

(original) (raw)


On 26 Jun 2014 01:13, "Serhiy Storchaka" <storchaka@gmail.com> wrote:
\>
\> 25.06.14 16:29, Victor Stinner написав(ла):
\>>
\>> 2014-06-25 14:58 GMT+02:00 Serhiy Storchaka <storchaka@gmail.com>:
\>>>
\>>> Other benefit: patches exposed several bugs in code (mainly errors in
\>>> backporting from 3.x).
\>>
\>>
\>> Oh, interesting. Do you have examples of such bugs?
\>
\>
\> In posixpath branches for unicode and str should be reversed.
\> In multiprocessing .encode('utf-8') is applied on utf-8 encoded str (this is unicode string in Python 3). And there is similar error in at least one other place. Tests for bytearray actually test bytes, not bytearray. That is what I remember.

OK, \*that\* sounds like an excellent reason to keep the Unicode disabled builds functional, and make sure they stay that way with a buildbot: to help make sure we're not accidentally running afoul of the implicit interoperability between str and unicode when backporting fixes from Python 3.

Helping to ensure correct handling of str values makes this capability something of benefit to \*all\* Python 2 users, not just those that turn off the Unicode support. It also makes it a potentially useful testing tool when assessing str/unicode handling in general.

Regards,
Nick.

>
\>
\> \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_
\> Python-Dev mailing list
\> Python-Dev@python.org
\> https://mail.python.org/mailman/listinfo/python-dev
\> Unsubscribe: https://mail.python.org/mailman/options/python-dev/ncoghlan%40gmail.com