Mark Dickinson <dicki...@gmail.com> added the comment: > However, that header file was removed in this commit: > http://svn.python.org/view?view=rev&revision=71697
Hmm. That was me. > with this message: > Issue #4910: PyNumber_Int is deprecated in 3.0.1; will be removed in > 3.1. That's the message for r69517, I think, which just added an entry to Include/intobject.h. The message for r71697 was: "The comments at the top of intobject.h say that it will be removed in 3.1. Make it so." I'm not too sure of the history here, but I suspect that Include/intobject.h was at least partly an aid to porting the Python extension modules from 2.x to 3.0, rather than third-party modules. Christian, Benjamin: any comments? I'm -1 on resurrecting Include/intobject.h in its old location. I don't much like the idea of having a random include file that's no longer used by Python itself in the main Include directory; it'll likely succumb to bitrot before long. But maybe there's a place for 2-to-3 porting aids in the Tools directory, where there's less expectation that files are well-maintained? > Is is acceptable if I ship that header file in my distribution > packages of python-3.1.1 ? (possibly with a reworded deprecation > warning?) I can't see any problem with this. I agree the porting documentation needs to be updated, whatever happens. ---------- assignee: -> georg.brandl components: +Documentation nosy: +benjamin.peterson, christian.heimes, georg.brandl, mark.dickinson _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue7353> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
