On donderdag, nov 28, 2002, at 11:44 Europe/Amsterdam, Martin v. Löwis wrote:
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).
Well.... First of all, warning people about something without giving them a way to do something about it isn't really good style. Second, it will *not* break in 2.4, because I'm just going to add an O& formatter PyMac_Parse32BitIntWithoutSillyComplaints, which will take any reasonable type on the Python side and just return the lower 32 bits. Actually, I could make that fix *now*, but I would still be stuck with the stupid warnings:-( -- - Jack Jansen <Jack.Jansen@oratrix.com> http://www.cwi.nl/~jack - - If I can't dance I don't want to be part of your revolution -- Emma Goldman -