This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author jaraco
Recipients brett.cannon, dstufft, eric.araujo, jaraco, ncoghlan, python-dev
Date 2016-09-01.18:03:54
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1472753034.21.0.00435700064915.issue27919@psf.upfronthosting.co.za>
In-reply-to
Content
Thanks, Nick. I've also observed that the package that was mentioned in the comments was "Numeric Python" and I confirmed that numpy is not currently using this option, so that's a positive indication that it's unneeded. I've also reached out to New Relic and invited them to comment here about the value they get (if any) from the option.

I've committed the deprecation warning as well. I'll plan to mirror this deprecation warning in Setuptools to get faster feedback. I'm open to reverting this change before the final release of Python 3.6 if it turns out to be a necessary feature.

As for your first suggestion - having Setuptools disable the behavior, I'm not sure Setuptools has the context to disable the behavior, because at the time pip is invoking the install command, Setuptools doesn't know whether pip is going to install the packages into platlib or elsewhere. At least, that's my presumption; I haven't dived into the code. I'm okay with not having a workaround if later versions of Setuptools and Python can disable the functionality without breaking anything but the most obscure packages.
History
Date User Action Args
2016-09-01 18:03:54jaracosetrecipients: + jaraco, brett.cannon, ncoghlan, eric.araujo, python-dev, dstufft
2016-09-01 18:03:54jaracosetmessageid: <1472753034.21.0.00435700064915.issue27919@psf.upfronthosting.co.za>
2016-09-01 18:03:54jaracolinkissue27919 messages
2016-09-01 18:03:54jaracocreate