A RetroSearch Logo

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

Search Query:

Showing content from http://mail.python.org/pipermail/python-dev/2002-November/030531.html below:

[Python-Dev] int/long FutureWarning

[Python-Dev] int/long FutureWarning [Python-Dev] int/long FutureWarningMartin v. Löwis martin@v.loewis.de
28 Nov 2002 11:44:12 +0100
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




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