➜

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, dmalcolm, loewis, ncoghlan, pitrou, skrah, teoliphant, vstinner
Date 2012-08-02.23:01:46
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <2BF1B7E4-F115-4C3C-8011-822965DF8A98@gmail.com>
In-reply-to <1343946483.82.0.619793557796.issue15540@psf.upfronthosting.co.za>
Content 
On Aug 2, 2012, at 5:28 PM, Antoine Pitrou wrote:

> 
> Antoine Pitrou added the comment:
> 
> Agreed with Martin. Byte-swapped unicode data in unicode objects doesn't make sense, since it will break the semantics of many operations. If numpy wants to support byte-swapped unicode data (what for?), they should store it in a different object type.

This is a mis-understanding of what NumPy does and why.    There is a need to byte-swap only when the data is stored on disk in the reverse order from the native machine (i.e. NumPy is pointing to memory-mapped data).    

The byte-swapping must be done prior to conversion to a Python Unicode-Object when selecting data out of the array.   

-Travis
History
Date User Action Args
2012-08-02 23:01:48teoliphantsetrecipients: + teoliphant, loewis, ncoghlan, pitrou, vstinner, Arfrever, alex, skrah, dmalcolm
2012-08-02 23:01:47teoliphantlinkissue15540 messages
2012-08-02 23:01:46teoliphantcreate