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 pitrou
Recipients gregory.p.smith, jcon, mark.dickinson, ncoghlan, pitrou, skrah, teoliphant, vstinner, xuanji
Date 2011-08-23.15:31:53
SpamBayes Score 8.020452e-09
Marked as misclassified No
Message-id <1314113374.3485.31.camel@localhost.localdomain>
In-reply-to <1314112959.68.0.451269179975.issue5231@psf.upfronthosting.co.za>
Content
> However, requiring an explicit two-step process for any other casting
> (i.e. take a 1-D view, then a shaped view of that flat 1-D view) also
> sounds reasonable.
> 
> So I agree with Victor that 1-D bytes -> any shape/format and any
> shape/format -> 1-D bytes should be allowed, but I think we should
> hold off on allowing arbitrary transformations in a single step.

Converting to 1-D bytes is my main motivation for this feature request,
so I'm fine with such a limitation.

The point is to be able to do in Python what we can do in C, take an
arbitrary buffer and handle it as pure bytes (for I/O or cryptography
purposes, for example).
History
Date User Action Args
2011-08-23 15:31:53pitrousetrecipients: + pitrou, gregory.p.smith, teoliphant, mark.dickinson, ncoghlan, vstinner, skrah, xuanji, jcon
2011-08-23 15:31:53pitroulinkissue5231 messages
2011-08-23 15:31:53pitroucreate