Message 167109 - 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	skrah
Recipients	mark.dickinson, meador.inge, pitrou, skrah, vstinner
Date	2012-08-01.10:07:10
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1343815631.76.0.659113500021.issue13072@psf.upfronthosting.co.za>
In-reply-to

Content
Is it possible without too much effort to keep the old behavior ('u' -> Py_UNICODE)? Then I'd say that should go into 3.3. The problem with the current behavior is that it's neither backwards compatible nor PEP-3118 compliant. If it is too much work to restore the status quo, we could leave this change with the excuse that 'u' is probably not used very often.

Is it possible without too much effort to keep the old behavior
('u' -> Py_UNICODE)? Then I'd say that should go into 3.3.


The problem with the current behavior is that it's neither backwards
compatible nor PEP-3118 compliant.

If it is too much work to restore the status quo, we could leave this
change with the excuse that 'u' is probably not used very often.

History
Date	User	Action	Args
2012-08-01 10:07:11	skrah	set	recipients: + skrah, mark.dickinson, pitrou, vstinner, meador.inge
2012-08-01 10:07:11	skrah	set	messageid: <1343815631.76.0.659113500021.issue13072@psf.upfronthosting.co.za>
2012-08-01 10:07:10	skrah	link	issue13072 messages
2012-08-01 10:07:10	skrah	create