Terry J. Reedy <[EMAIL PROTECTED]> added the comment: 2.6 is, as far as I know, intended to be backwards compatible except for where it fixes bugs. Upgrading to 2.6 does (should) not change strings (type str) to unicode. Only importing the appropriate __future__ or upgrading to 3.0 will do that. I have no idea what Django does.
The 3 lines of code you posted gives exactly the same traceback in my copy of 2.5 as the one you posted. _______________________________________ Python tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue4329> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
