Jason R. Coombs added the comment:
I'm not sure I understand the justification. If the patch serves a logical
purpose, and distutils isn't deprecated in the current development line, then I
would suggest we apply the patch. If we don't fix the behavior today, then the
library will be in the
Éric Araujo added the comment:
Thanks for weighing in. (Adding Donald as pip representative.)
I'd prefer the patch be accepted or rejected on merits.
The current patch is incomplete because not fully backward-compatible: even if
we imported “distutils.debug” everywhere, we’d still need to
Jason R. Coombs added the comment:
That's entirely reasonable. I thought maybe that was the case.
My instinct is that 100% backward compatibility may not be necessary,
especially if setuptools and pip are in the loop and can assure compatibility
at some level. I'll dig deeper into the issue
Jason R. Coombs added the comment:
Searching through the setuptools code base, there's no code reference to DEBUG
and only one comment referencing DISTUTILS_DEBUG (which I'm suspicious may be a
legacy artifact). In any case, I'm mostly confident that applying the patch as
presented would have
Éric Araujo added the comment:
I see the value in this small change, but this could only be changed in 3.5,
making it mostly irrelevant for potential clients (i.e. packaging tools that
extend distutils), as they keep compatibility with 2.7. In the absence of
requests by developers of these
Chris Jerdonek added the comment:
I meant to comment on the patch earlier.
The fix here isn't as simple as I had originally suggested. The patch has to
be constructed more carefully to be more fully backwards compatible. For
example, it shouldn't break code that imports DEBUG from modules,
Changes by Chris Jerdonek chris.jerdo...@gmail.com:
--
keywords: -easy
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue16989
___
___
Jeff Knupp added the comment:
Patch uploaded.
Note that updating the test_distutils.core test revealed that the test was
importing DEBUG from the wrong module (which only existed because
distutils.core use the 'from ... import DEBUG' form). I've corrected the import
and updated the test
New submission from Chris Jerdonek:
This issue is to allow distutils's debug mode [1] to be enabled more easily
(e.g. programmatically).
Currently, for example, distutils.core does the following:
from distutils.debug import DEBUG
(from
