➜

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 teoliphant
Recipients Arfrever, alex, certik, dmalcolm, loewis, ncoghlan, pitrou, skrah, teoliphant, vstinner
Date 2012-08-02.23:26:41
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <68DC345B-7E22-4D15-86F1-E1B2E7D8AC1A@gmail.com>
In-reply-to <1343948839.3368.4.camel@localhost.localdomain>
Content 
On Aug 2, 2012, at 6:09 PM, Antoine Pitrou wrote:

> 
> Antoine Pitrou added the comment:
> 
>> The byte-swapping must be done prior to conversion to a Python
>> Unicode-Object when selecting data out of the array.
> 
> But then it shouldn't affect the invariants which are commented out in
> Dave's patch.
> 

My impression is that Python should not have to change anything, but NumPy needs to adapt to the new Unicode concepts (which I think are great, by the way --- I'm a big supporter of getting rid of the wide/narrow build distinction). 

> ----------
> 
> _______________________________________
> Python tracker <report@bugs.python.org>
> <http://bugs.python.org/issue15540>
> _______________________________________
History
Date User Action Args
2012-08-02 23:26:42teoliphantsetrecipients: + loewis, ncoghlan, pitrou, vstinner, Arfrever, certik, alex, skrah, dmalcolm
2012-08-02 23:26:41teoliphantlinkissue15540 messages
2012-08-02 23:26:41teoliphantcreate