Greg Ewing <[EMAIL PROTECTED]> wrote: > > Nick Coghlan wrote: > > > I think the point is for there to be something in the standard library > > or Python core that makes it easy for a consumer to *copy* the data to a > > contiguous memory segment in the event the consumer can't directly > > handle non-contiguous data > > It would be even more useful if the destination could > be non-contiguous as well, but with a different stride. > Then you could go from contiguous to non-contiguous, > non-contiguous to contiguous, or repack between two > different non-contiguous formats.
With writable views, presumably that would be a[w:x] = b[y:z], for any such operation (assuming compatible values, etc.). - Josiah _______________________________________________ Python-3000 mailing list [email protected] http://mail.python.org/mailman/listinfo/python-3000 Unsubscribe: http://mail.python.org/mailman/options/python-3000/archive%40mail-archive.com
