Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2006-June/065684.html below:

[Python-Dev] Is "t#" argument format meant to be char buffer, or just read-only?

• Previous message: [Python-Dev] Is "t#" argument format meant to be char buffer, or just read-only?
• Next message: [Python-Dev] Is "t#" argument format meant to be char buffer, or just read-only?
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Thomas Heller wrote:

> I think that hexlify should be able to use any buffer object that has
> a readable memory block, not only those with charbuffers.
> 
> The docs say that the binascii methods are used to "convert between binary
> and various ASCII-encoded binary representations".

So why the heck is hexlify looking for charbuffers and not
byte buffers in the first place?

--
Greg

• Previous message: [Python-Dev] Is "t#" argument format meant to be char buffer, or just read-only?
• Next message: [Python-Dev] Is "t#" argument format meant to be char buffer, or just read-only?
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4