[Python-Dev] int/long FutureWarning

[Martin v. Löwis]

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

> Well.... First of all, warning people about something without giving
> them a way to do something about it isn't really good style. 

Whom are you directing this observation at?

I was merely pointing out that the warning is factually correct and
indicates a real future problem; I did not consider style at all.

> 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.

It would be better if you could just contribute a patch to add such an
argument parser to the standard ParseTuple implementation, instead of
coming up with proprietary Mac solutions.

When I said "it will break", I meant "unless action is taken", of
course.

Regards,
Martin