Marc-Andre Lemburg wrote:
> 
>> Ned Deily <nad@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.