Christian Tismer firstname.lastname@example.org writes:
p.s.: I believe some automatic source analysis and rewrite might pay off in other areas as well. Grepping through the sources, there are still very many similar patterns of PyArg_ParseTupleXXX calls, which could be replaced by less general, optimized versions. This would even *not* cause code bloat, since all those calling sequences would be smaller than now.
Well, yes. C sucks seriously for things like this, though. It's frankly embarassing that *every* time, say, ''.split() is called, some silly string is being parsed. Unclear what to do about this (excpet PyPy, I guess).