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-17.22:31:37
SpamBayes Score 1.1076352e-07
Marked as misclassified No
Message-id <1232231499.72.0.627836745.issue4910@psf.upfronthosting.co.za>
In-reply-to
Content
Here's a patch that deprecates PyNumber_Int in favour of PyNumber_Long:

- move PyNumber_Int definition from abstract.h to intobject.h (and
  fix up comments at the top of intobject.h)
- mark PyNumber_Int as deprecated in the c-api docs, with a promise
  to remove it for 3.1.

I suppose that in theory this goes too far:  we should really deprecate in 
3.1 and remove in 3.2.  But given all the other stuff that's going on for 
3.0.1, this doesn't seem too bad.  Benjamin, what do you think?

N.B.  We should remember to actually remove intobject.h for 3.1. :)
History
Date User Action Args
2009-01-17 22:31:40mark.dickinsonsetrecipients: + mark.dickinson, benjamin.peterson
2009-01-17 22:31:39mark.dickinsonsetmessageid: <1232231499.72.0.627836745.issue4910@psf.upfronthosting.co.za>
2009-01-17 22:31:38mark.dickinsonlinkissue4910 messages
2009-01-17 22:31:38mark.dickinsoncreate