> No, that does *not* help (as I have explained umpteen times). As the > warning is given by the parser there is absolutely nothing you can do > about it with a PyArg_ParseTuple converter. As I have explained twice as often, you need to add an L to the constants. > There are of course workarounds (like adding, for 2.3 only, an "L" > to all the constants in addition to the custom converter) but that would > be silly because things will work again in 2.4. No, they won't. If you just add the L, you will get OverflowErrors, unless you also modify the the ParseTuple calls. Regards, Martin
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