Message95470
> 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. |
|
Date |
User |
Action |
Args |
2009-11-19 14:07:26 | mark.dickinson | set | recipients:
+ mark.dickinson, skip.montanaro, georg.brandl, christian.heimes, benjamin.peterson, dmalcolm |
2009-11-19 14:07:25 | mark.dickinson | set | messageid: <1258639645.94.0.636054575624.issue7353@psf.upfronthosting.co.za> |
2009-11-19 14:07:24 | mark.dickinson | link | issue7353 messages |
2009-11-19 14:07:23 | mark.dickinson | create | |
|