On Sun, 18 May 2008 22:59:05 +0000, Dan Lenski wrote:
> So here's what I don't understand. Why doesn't the "t#" argument
> specifier support read-write buffers as well as read-only buffers?
> Aren't read-write buffers a *superset* of read-only buffers?? Is there
> something I'm doing wrong or a quick fix to get this to work
> appropriately?
So... I've answered my own question on this. I had a look in getargs.c,
and apparently the "t#" argument specifier only accepts *character-based*
readable buffers.
Is there any chance anyone of adding an argument specifier for readable
buffers in general? Say, "r#"?
Can anyone explain to me the rationale for having some data type support
the readable buffer interface, but /NOT/ the character-based buffer
interface? I can't find any information that explains the fundamental
distinction between the two... and I don't see why array('B') shouldn't
support both.
Dan
_______________________________________________
Python-Dev mailing list
[email protected]
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
