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 loewis
Recipients Alexander.Belopolsky, Arfrever, Dag.Sverre.Seljebotn, belopolsky, christian.heimes, georg.brandl, loewis, mark.dickinson, meador.inge, ncoghlan, pitrou, python-dev, scoder, skrah, vstinner
Date 2012-09-01.16:06:17
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <50423277.1020207@v.loewis.de>
In-reply-to <1346509461.82.0.800548746043.issue15814@psf.upfronthosting.co.za>
Content
Am 01.09.12 16:24, schrieb Stefan Krah:
> Does "byte arrays" include 'b' and 'c' or just 'B'? I don't see a reason
> to allow 'B' but not the others.

Either type is fine with me. It's the multi-dimensional aspect I'd like
to ban.

> My reasoning was: If non-contiguous arrays are allowed (and I think they
> should be), why not allow multi-dimensional arrays, too?

I think neither should be allowed. The explicit request (from Antoine)
was that memoryviews of bytes objects should be hashable. I haven't
heard anybody asking for something more general (but I could see that
people want to hash other memory blocks as well, such as mmap views).

I can see that it is tempting to provide the most general definition,
but see where this approach got us. It's always easier to widen an
interface later than to narrow it.
History
Date User Action Args
2012-09-01 16:06:18loewissetrecipients: + loewis, georg.brandl, mark.dickinson, ncoghlan, belopolsky, pitrou, scoder, vstinner, christian.heimes, Arfrever, skrah, meador.inge, Alexander.Belopolsky, python-dev, Dag.Sverre.Seljebotn
2012-09-01 16:06:18loewislinkissue15814 messages
2012-09-01 16:06:17loewiscreate