[Distutils] tourist here, with a dumb RTFM question

Nick Coghlan ncoghlan at gmail.com
Sat Mar 8 16:24:12 CET 2014

On 9 Mar 2014 01:20, "Nick Coghlan" <ncoghlan at gmail.com> wrote:
> On 9 Mar 2014 00:26, "Jason R. Coombs" <jaraco at jaraco.com> wrote:
> >
> > I had incorrectly assessed the potential impact of this change. I had
expected the impact to be minor and isolated. I underestimated the number
of systems that automatically upgrade Setuptools as well as the number of
packages that could be using Features. I relied too heavily on the
DeprecationWarning to have flagged the breakage (to package maintainers and
their users). I had expected issues like you raised in this post to have
been hashed out or at least raised long before I considered the release.
> Ouch, I just realised this is likely a nasty consequence of the decision
we made in CPython quite some time ago to silence deprecation warnings by
> The reason we did that was because *end users* were getting the warnings,
not just developers of affected projects.
> At the same time, unittest and other test runners were updated to enable
the warnings, under the theory that at least projects with reasonable test
coverage would still receive advance notice of the problem, providing a
counterbalance to the risks introduced by silencing them by default.

Oops, missed a key paragraph here: the reason this is a problem for
setuptools deprecations in particular is that most developers are unlikely
to run their setup.py file under the control of a test runner that would
enable the warning.

> Perhaps once wheel files are more widespread, we can look at having pip
always enable deprecation warnings when building from source.
> Cheers,
> Nick.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/distutils-sig/attachments/20140309/9716714e/attachment.html>

More information about the Distutils-SIG mailing list