[Python-Dev] Int FutureWarnings and other 2.4 TODOs
Kalle Svensson
kalle at lysator.liu.se
Tue Nov 25 15:32:58 EST 2003
[Guido van Rossum]
> There's a bunch of FutureWarnings e.g. about 0xffffffff<<1 that
> promise they will disappear in Python 2.4. If anyone has time to
> fix these, I'd appreciate it. (It's not just a matter of removing
> the FutureWarnings -- you actually have to implement the promised
> future behavior. :-) I may get to these myself, but they're not
> exactly rocket science, so they might be a good thing for a
> beginning developer (use SF please if you'd like someone to review
> the changes first).
I've submitted a patch (http://python.org/sf/849227). And yes,
somebody should probably take a good look at it before applying. The
(modified) test suite does pass on my machine, but that's all. I may
well have forgotten to add tests for new special cases, and I'm not
the most experienced C programmer on the block either.
As a side note, I think that line 233 in Lib/test/test_format.py
if sys.maxint == 2**32-1:
should be
if sys.maxint == 2**31-1:
but I didn't include that in the patch or submit a bug report.
Should I?
Peace,
Kalle
--
Kalle Svensson, http://www.juckapan.org/~kalle/
Student, root and saint in the Church of Emacs.
More information about the Python-Dev
mailing list