Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2001-August/017086.html below:

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

• Previous message: [Python-Dev] non-standard HTML tags in 2.1.1 documentation
• Next message: [Python-Dev] PyArg_ParseTuple format string: "h" vs. "H"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

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

• Previous message: [Python-Dev] non-standard HTML tags in 2.1.1 documentation
• Next message: [Python-Dev] PyArg_ParseTuple format string: "h" vs. "H"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4