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 martin.panter
Recipients Filip Haglund, abarry, martin.panter
Date 2016-01-10.22:04:57
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1452463497.42.0.480730644255.issue26077@psf.upfronthosting.co.za>
In-reply-to
Content
I think which technique (copy or view) is better depends on the situation. If you are making a large temporary slice, a view may be more efficient. But if you are making a long-term slice and don’t need the original any more, a copy would allow the original memory to be freed early.

Do you have any use cases? You can already get a kind of slice view into bytes etc by using memoryview().
History
Date User Action Args
2016-01-10 22:04:57martin.pantersetrecipients: + martin.panter, abarry, Filip Haglund
2016-01-10 22:04:57martin.pantersetmessageid: <1452463497.42.0.480730644255.issue26077@psf.upfronthosting.co.za>
2016-01-10 22:04:57martin.panterlinkissue26077 messages
2016-01-10 22:04:57martin.pantercreate