[Python-Dev] PyArg_ParseTuple format string: "h" vs. "H"

[Just van Rossum]

I was just bit by an older PyArg_ParseTuple format string behavior change: these
days (since 2.1?) "h" barfs when you feed it an unsigned short value (even if
it's within 16 bits). So ok, I updated my code to use "H" instead, only to find
out hours later that "H" didn't exist yet in 1.5.2. I really need to be
compatible with both so I'll have to work around it :-(

Was this change really neccesary?

Just