Message 76469 - Python tracker

➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author	terry.reedy
Recipients	mbecker, terry.reedy, vstinner
Date	2008-11-26.15:20:56
SpamBayes Score	0.00025535104
Marked as misclassified	No
Message-id	<1227712935.83.0.458585259912.issue4329@psf.upfronthosting.co.za>
In-reply-to

Content
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.

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.

History
Date	User	Action	Args
2008-11-26 15:22:16	terry.reedy	set	recipients: + terry.reedy, vstinner, mbecker
2008-11-26 15:22:15	terry.reedy	set	messageid: <1227712935.83.0.458585259912.issue4329@psf.upfronthosting.co.za>
2008-11-26 15:20:58	terry.reedy	link	issue4329 messages
2008-11-26 15:20:57	terry.reedy	create