skipitem() in getargs.c missing some types

[hacocuk]

BPO	893549
Nosy	@birkenfeld

^{Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.}

Show more details

GitHub fields:

assignee = None
closed_at = <Date 2005-09-14.19:32:23.000>
created_at = <Date 2004-02-09.17:30:50.000>
labels = ['library']
title = 'skipitem() in getargs.c missing some types'
updated_at = <Date 2005-09-14.19:32:23.000>
user = 'https://bugs.python.org/hacocuk'

bugs.python.org fields:

activity = <Date 2005-09-14.19:32:23.000>
actor = 'georg.brandl'
assignee = 'none'
closed = True
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2004-02-09.17:30:50.000>
creator = 'hacocuk'
dependencies = []
files = []
hgrepos = []
issue_num = 893549
keywords = []
message_count = 6.0
messages = ['19951', '19952', '19953', '19954', '19955', '19956']
nosy_count = 4.0
nosy_names = ['georg.brandl', 'hacocuk', 'subik', 'ringerc']
pr_nums = []
priority = 'normal'
resolution = 'fixed'
stage = None
status = 'closed'
superseder = None
type = None
url = 'https://bugs.python.org/issue893549'
versions = ['Python 2.2']

[hacocuk]

python 2.2.3
looks like skipitem in getargs.c is missing some types
'k' for example

[birkenfeld]

Logged In: YES
user_id=1188172

The missing types are u, u#, es, es#, et, et#, k, K, I, U,
t#, w, w# and maybe (...)

I don't know whether this is of any significance though.

[subik]

Logged In: YES
user_id=784012

this bug is still presented in later versions 2.3, 2.4.
We have real problem with it (see.
http://bugs.scribus.net/view.php?id=2018).
Broken PyArg_ParseTupleAndKeywords in skipitem() (getargs.c)
causes "impossible<bad format char>" exception by missing case
conditions.

I would like to please developers for fixing (or we will be forced to
provide a patch (which will force us to know Python guts (etc.))).

[ringerc]

Logged In: YES
user_id=639504

It matters all right. Just wasted a bunch of time tracking
this down into the Python sources and confirming it was a
Python bug. It's really nasty for 'es'.

This will cause bizarre errors for
PyArg_ParseTupleAndKeywords(...) calls using the unsupported
format strings after the | optional argument barrier. The
errors will always contain the string:

impossible<bad format char>

The error will, of course, only turn up if the user omits
one or more of the arguments with unsupported formats.

[birkenfeld]

Logged In: YES
user_id=1188172

I submitted a patch (bpo-1212928) which fixes that.

[birkenfeld]

Logged In: YES
user_id=1188172

Fixed with patch bpo-1212928.