Message 168368 - 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	ncoghlan
Recipients	loewis, ncoghlan, skrah, teoliphant
Date	2012-08-16.10:30:22
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1345113022.81.0.173485184838.issue15625@psf.upfronthosting.co.za>
In-reply-to

Content
I wouldn't change the export formats used for the 'u' typecode at all in 3.4 - I'd add new typecodes to array that match any new struct format characters and are exported accordingly. 'u' would never become a formally defined struct character, instead lingering in the array module as a legacy of the narrow/wide build distinction. And good point that U would need to match UCS-4 to be consistent with NumPy. Perhaps we can just add 'U' in 3.4 and forget about UCS-2 entirely?

I wouldn't change the export formats used for the 'u' typecode at all in 3.4 - I'd add new typecodes to array that match any new struct format characters and are exported accordingly. 'u' would *never* become a formally defined struct character, instead lingering in the array module as a legacy of the narrow/wide build distinction.

And good point that U would need to match UCS-4 to be consistent with NumPy. Perhaps we can just add 'U' in 3.4 and forget about UCS-2 entirely?

History
Date	User	Action	Args
2012-08-16 10:30:22	ncoghlan	set	recipients: + ncoghlan, loewis, teoliphant, skrah
2012-08-16 10:30:22	ncoghlan	set	messageid: <1345113022.81.0.173485184838.issue15625@psf.upfronthosting.co.za>
2012-08-16 10:30:22	ncoghlan	link	issue15625 messages
2012-08-16 10:30:22	ncoghlan	create