[Python-Dev] Is "t#" argument format meant to be char buffer, or just read-only?
Greg Ewing
greg.ewing at canterbury.ac.nz
Thu Jun 8 10:52:01 CEST 2006
More information about the Python-Dev mailing list
Thu Jun 8 10:52:01 CEST 2006
- 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 ]
More information about the Python-Dev mailing list