Message169498
OK, I can understand the desire to make memoryviews be bytes-like objects (though to my mind, bytes is "frozen" in a very different way...)
If so, and it is deemed worth it, my suggestion is to add a new PyBUF_CONST flag to the buffer acquisition in that case (which can not be used together with PyBUF_WRITABLE). Given that flag, the exporter guarantees that the contents does not change (or fails to give away a buffer).
Perhaps it could be possible for hash() to try to re-acquire a const buffer, so that some buffers are hashable (by contents) and others not.
(I really think relying on buffers that are not writeable to be constant is dangerous. A readonly memoryview could for instance point straight to the live output of a webcam.) |
|
Date |
User |
Action |
Args |
2012-08-31 03:47:34 | Dag.Sverre.Seljebotn | set | recipients:
+ Dag.Sverre.Seljebotn, loewis, georg.brandl, mark.dickinson, ncoghlan, belopolsky, pitrou, scoder, vstinner, christian.heimes, Arfrever, skrah, meador.inge |
2012-08-31 03:47:33 | Dag.Sverre.Seljebotn | set | messageid: <1346384853.22.0.857205936594.issue15814@psf.upfronthosting.co.za> |
2012-08-31 03:47:32 | Dag.Sverre.Seljebotn | link | issue15814 messages |
2012-08-31 03:47:32 | Dag.Sverre.Seljebotn | create | |
|