Issue 7018: Recommend "*" over "#" in getargs.c typecodes (original) (raw)

Issue7018

Created on 2009-09-29 10:59 by pitrou, last changed 2022-04-11 14:56 by admin. This issue is now closed.

Messages (3)
msg93276 - (view) Author: Antoine Pitrou (pitrou) * (Python committer) Date: 2009-09-29 10:59
In « Parsing arguments and building values » (c-api/arg.html), it should be made clear that "*" typecodes are recommended over the "#" typecodes, which are inherently unsafe. (more generally, the page is totally unreadable, a solution might be to group the typecodes by family: numbers, strings/buffers, objects; also, there are so many choices that it's confusing which ones should be preferred)
msg93279 - (view) Author: Antoine Pitrou (pitrou) * (Python committer) Date: 2009-09-29 11:14
This only really applies in 2.x, actually. In 3.x, "#" should be discouraged for another reason: it is overly strict and will only accept pure read-only objects (which don't have a bf_releasebuffer method); even bytearrays will be rejected.
msg241631 - (view) Author: Mark Lawrence (BreamoreBoy) * Date: 2015-04-20 11:16
The 3.x arg.html seems a great improvement to my eye compared to the 2.x version so I'd guess this can be closed as out of date.
History
Date User Action Args
2022-04-11 14:56:53 admin set github: 51267
2020-10-22 22:32:21 iritkatriel set status: open -> closedresolution: out of datestage: resolved
2019-03-15 22:08:27 BreamoreBoy set nosy: - BreamoreBoy
2015-04-20 11:16:54 BreamoreBoy set nosy: + BreamoreBoymessages: +
2010-10-29 10:07:21 admin set assignee: georg.brandl -> docs@python
2009-09-29 11:14:48 pitrou set messages: +
2009-09-29 10:59:14 pitrou create