test_support.have_unicode
The test_support unit has this have_unicode. Do we need the Python's test unit to be *that* backward compatible? Is there still an implementation of Python that doesn't support unicode? If there is, should the test suite care? As a side question. Considering that I'm not sure whether have_unicode is relevant or not, is it more appropriate to create a ticket for it or to ask python-dev? Virgil Dupras
On Tue, Mar 18, 2008 at 8:18 AM, Virgil Dupras <hsoft@hardcoded.net> wrote:
The test_support unit has this have_unicode. Do we need the Python's test unit to be *that* backward compatible? Is there still an implementation of Python that doesn't support unicode? If there is, should the test suite care?
Python 2.x can be compiled without Unicode.
As a side question. Considering that I'm not sure whether have_unicode is relevant or not, is it more appropriate to create a ticket for it or to ask python-dev?
Virgil Dupras _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/musiccomposition%40gmail.c...
The test_support unit has this have_unicode. Do we need the Python's test unit to be *that* backward compatible? Is there still an implementation of Python that doesn't support unicode? If there is, should the test suite care?
It's still intended that you can build Python 2.6 without Unicode support, and that the test suite "mostly" works. If it doesn't, it's up to users who care about that feature to provide fixes, but you should not actively break it. Regards, Martin
Martin v. Löwis schrieb:
It's still intended that you can build Python 2.6 without Unicode support, and that the test suite "mostly" works.
If it doesn't, it's up to users who care about that feature to provide fixes, but you should not actively break it.
About two months ago I fixed the most critical bugs but the unicode free build is treated like a poor cousin at best. It's neither actively developed nor tested in regular intervals. IMO it's a deprecation candiate. Christian
About two months ago I fixed the most critical bugs but the unicode free build is treated like a poor cousin at best. It's neither actively developed nor tested in regular intervals. IMO it's a deprecation candiate.
In the sense that 3k won't support it anymore - certainly. In the sense that it will be removed in 2.7: Why? I'd rather say it's unmaintained, not deprecated. Regards, Martin
On Tue, Mar 18, 2008 at 9:25 AM, "Martin v. Löwis" <martin@v.loewis.de> wrote:
About two months ago I fixed the most critical bugs but the unicode free build is treated like a poor cousin at best. It's neither actively developed nor tested in regular intervals. IMO it's a deprecation candiate.
In the sense that 3k won't support it anymore - certainly.
In the sense that it will be removed in 2.7: Why?
I'd rather say it's unmaintained, not deprecated.
Right. It's a Py3k warning candidate. -- --Guido van Rossum (home page: http://www.python.org/~guido/)
participants (5)
-
"Martin v. Löwis" -
Benjamin Peterson -
Christian Heimes -
Guido van Rossum -
Virgil Dupras