[issue13994] incomplete revert in 2.7 Distutils left two copies of customize_compiler
Marc-Andre Lemburg
report at bugs.python.org
Fri Apr 20 11:12:28 CEST 2012
Marc-Andre Lemburg <mal at egenix.com> added the comment:
Marc-Andre Lemburg wrote:
>
>> Ned Deily <nad at acm.org> added the comment:
>>
>> That's unfortunate. But the documented location for customize_compiler is and, AFAIK, had always been in distutils.sysconfig. It was an inadvertent consequence of the bad revert during the 2.7 development cycle that a second copy was made available in distutils.ccompiler. That change was not supposed to be released in 2.7 and was never documented. So I don't think there is anything that can or needs to be done as this point in Python itself. Other opinions?
>
> Excuse me, Ned, but that's not how we do approach dot releases in Python.
>
> Regardless of whether the documentation was fixed or not, you cannot
> simply remove a non-private function without making sure that at least
> the import continues to work.
Turns out, the "fix" broke all our packages for Python 2.7.3 and
I can hardly believe we're the only ones affected by this.
----------
_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue13994>
_______________________________________
More information about the Python-bugs-list
mailing list