Steve Holden st...@holdenweb.com added the comment:
With the 2.7 release now completed should we close this issue? There's nothing
to be done about the 2.6 issue.
--
nosy: +holdenweb
___
Python tracker rep...@bugs.python.org
Ronald Oussoren ronaldousso...@mac.com added the comment:
I agree, this issue can be closed as there's nothing useful we can do at this
point in time.
--
resolution: - wont fix
stage: - committed/rejected
status: open - closed
___
Python tracker
Ronald Oussoren ronaldousso...@mac.com added the comment:
But should PYTHON_API_VERSION be increased for the 2.7 release?
I think it should because of the binary incompatible differences between 2.5
and 2.6. In a perfect world that would have resulted in an increase of
PYTHON_API_VERSION
Antoine Pitrou pit...@free.fr added the comment:
But should PYTHON_API_VERSION be increased for the 2.7 release?
Sounds like a good idea.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue8118
Antoine Pitrou pit...@free.fr added the comment:
Is PYTHON_API_VERSION actually useful right now? It seems to me that we need
Martin's ABI stability PEP to be implemented before extension modules can be
safely shared between several non-bugfix releases.
--
nosy: +loewis, pitrou
Martin v. Löwis mar...@v.loewis.de added the comment:
Is PYTHON_API_VERSION actually useful right now? It seems to me that
we need Martin's ABI stability PEP to be implemented before extension
modules can be safely shared between several non-bugfix releases.
Today, PYTHON_API_VERSION
New submission from Ronald Oussoren ronaldousso...@mac.com:
If I understand the code correct Python 2.6 has the same value for
PYTHON_API_VERSION, even though extensions are not compatible.
In particular: when you compile an extension that uses PyInt_Check with
python2.6 and load that
