Stefan Krah added the comment: Thanks for the detailed report! Making a private copy of 'format' for each memoryview generally sounds like the best solution. However, format strings can be arbitrarily large, so we'd need to store the copy in the ob_array after shape, strides and suboffsets.
This of course would slow down memoryview creation in the general case. Given that the disappearing format strings are only created during casting, I think we can get away with a local solution (see patch). ---------- Added file: http://bugs.python.org/file37881/issue22668-2.diff _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue22668> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
