➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author mark.dickinson
Recipients benjamin.peterson, mark.dickinson
Date 2009-01-15.19:21:27
SpamBayes Score 0.001004861
Marked as misclassified No
Message-id <1232047289.09.0.290533960168.issue4910@psf.upfronthosting.co.za>
In-reply-to
Content 
> I wonder if we should mark
> PyNumber_Long as deprecated in the docs, though.

It would be nice to standardize on one of (PyNumber_Long, PyNumber_Int) 
and document the other as deprecated.

Maybe it would make more sense to stick with PyNumber_Long and deprecate 
PyNumber_Int, though?  It would make 2.x -> 3.x transitions easier, and 
would be consistent with some of the rest of the API:  we seem to be 
using PyLong_Check in preference to PyInt_Check in current code...
History
Date User Action Args
2009-01-15 19:21:29mark.dickinsonsetrecipients: + mark.dickinson, benjamin.peterson
2009-01-15 19:21:29mark.dickinsonsetmessageid: <1232047289.09.0.290533960168.issue4910@psf.upfronthosting.co.za>
2009-01-15 19:21:28mark.dickinsonlinkissue4910 messages
2009-01-15 19:21:27mark.dickinsoncreate