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 pradyunsg
Recipients dstufft, eric.smith, pradyunsg, serhiy.storchaka, webknjaz
Date 2019-04-13.18:39:13
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CAPA-EqsPzRnzdXjyHNpPkg2EZVW8EQNhAjvWqt7kQEb4QGZJiQ@mail.gmail.com>
In-reply-to <1555082669.41.0.72121645453.issue36608@roundup.psfhosted.org>
Content
(Not sure how the Roundup handles email replies but I'm hoping this goes to
the right place)

I think it would be better if the downloading got invoked during the
interpreter build process -- to download the wheels and add them to the
final distribution. This lets us remove the wheels from the source
tree/version control and prevents needing to change the PEP for this change.

Functionally, I imagine having all the download logic in some sort of
ensurepip._bootstrap which has all the download logic and that getting
invoked in the build process. `python -m ensurepip` not hitting the
internet is a good invariant to keep.

On Fri, 12 Apr 2019 at 8:54 PM, Eric V. Smith <report@bugs.python.org>
wrote:

>
> Eric V. Smith <eric@trueblade.com> added the comment:
>
> And I don't mean to sound like a total downer. I just think it's important
> that we recognize all of the use cases.
>
> Thanks for your work on this.
>
> ----------
>
> _______________________________________
> Python tracker <report@bugs.python.org>
> <https://bugs.python.org/issue36608>
> _______________________________________
>
History
Date User Action Args
2019-04-13 18:39:13pradyunsgsetrecipients: + pradyunsg, eric.smith, serhiy.storchaka, dstufft, webknjaz
2019-04-13 18:39:13pradyunsglinkissue36608 messages
2019-04-13 18:39:13pradyunsgcreate