[issue1200] Allow array.array to be parsed by the t# format unit.

Mark Lawrence added the comment: OP has stated it's ok to close. -- nosy: +BreamoreBoy resolution: -> invalid status: open -> closed ___ Python tracker ___ _

[issue1200] Allow array.array to be parsed by the t# format unit.

Jeffrey Yasskin added the comment: I actually have no idea what I was trying to do when I ran into this. I think it was a use somewhere in the standard libraries rather than my own code, so if uses of t# are gone from there, I'd have no objections to closing this bug. -- __

[issue1200] Allow array.array to be parsed by the t# format unit.

Antoine Pitrou added the comment: I'm not sure what t# is for. Jeffrey, have you tried using y* instead? (you must call PyBuffer_Release at the end) -- ___ Python tracker ___ ___

[issue1200] Allow array.array to be parsed by the t# format unit.

Daniel Diniz added the comment: PyBUF_CHARACTER is now gone, and getargs.c reads: /*TEO: This can be eliminated --- here only for backward compatibility */ case 't': { /* 8-bit character buffer, read-only access */ -- nosy: +ajaksu2, pitrou stage: -> patc

[issue1200] Allow array.array to be parsed by the t# format unit.

Changes by Christian Heimes: -- keywords: +py3k priority: -> normal type: behavior -> rfe __ Tracker <[EMAIL PROTECTED]> __ ___ Python-bugs-lis

[issue1200] Allow array.array to be parsed by the t# format unit.

Guido van Rossum added the comment: Never mind. s/s# has explicit support for unicode. There is no t; t# requires a buffer that's not unicode (that's what PyBUF_CHARACTER amounts to). If there's one area I'd love to refactor it's getargs.c. What a sprawling mess! Also, we should kill PyBUF_CHA

[issue1200] Allow array.array to be parsed by the t# format unit.

Guido van Rossum added the comment: Hm, doesn't this make t and t# identical to s and s#? Or if there are still differences, are they still relevant? I vaguely recall that t and t# were introduced as variants of s and s# that requested char buffers. Since we're phasing out the whole idea of ch

[issue1200] Allow array.array to be parsed by the t# format unit.

New submission from Jeffrey Yasskin: This changes PyArg_ParseTuple()'s "t#" to request a PyBUF_SIMPLE buffer like all of the other buffer-using format units instead of PyBUF_CHARACTER. Objects with multi-byte units wind up byte-order-dependent. Alternately, it might make sense to have array.array