[Python-Dev] int/long FutureWarning

[Martin v. Löwis]

Jack Jansen <Jack.Jansen@oratrix.com> writes:

> I've been sick and tired of these warnings, especially since in 99.9%
> of the cases that you get the warning it is meaningless (as we are
> really taking about bitpatterns that have a special meaning in some C
> API). I personally haven't seen a single instance of the warning
> making sense.

I found that all those warnings are correct: in particular *when* the
constant is a bit pattern in some C API.

It means that your code *will* break in Python 2.4, unless you take
corrective action (which you cannot take at the moment). It will break
because ParseTuple will raise an OverflowError.

Regards,
Martin