Guido van Rossum <guido@python.org> writes: > There's no excuse for that any more. The 'i' and 'l' format chars of > PyArg_Parse* and PyInt_AsLong() both work for longs as well as for > ints. There is a change, of course: Passing 0xff<<24 to a function that uses the "i" converter will produce an OverflowError, whereas it previously would pass in the negative numbers. For cases of "I want 32 bits in an int", you'll have to accept both signed and unsigned 32 bits - something that is currently not supported in ParseTuple. 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