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 Segev Finer
Recipients Segev Finer
Date 2017-09-29.09:23:30
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1506677010.8.0.213398074469.issue31634@psf.upfronthosting.co.za>
In-reply-to
Content
wheel is quite prevalent nowadays. ensurepip even uses wheels of pip & setuptools itself. Installing wheel by default will bestow the following benefits:

1. pip's wheel cache will be enabled by default.
2. Users will be able to run setup.py bdist_wheel. Put simply, they will be able to build wheels.
3. Users will have access to the wheel command by default.

All those benefits will also apply in any created venv (Via the standard venv package). The external virtualenv package already does this https://github.com/pypa/virtualenv/tree/master/virtualenv_support. I often find myself installing wheel manually in any venv I create.

It shouldn't be too difficult to do, but it probably needs some agreement before being done.
History
Date User Action Args
2017-09-29 09:23:30Segev Finersetrecipients: + Segev Finer
2017-09-29 09:23:30Segev Finersetmessageid: <1506677010.8.0.213398074469.issue31634@psf.upfronthosting.co.za>
2017-09-29 09:23:30Segev Finerlinkissue31634 messages
2017-09-29 09:23:30Segev Finercreate