Is there a build script that automates vendoring in the latest pip? I see
checkpip.py, which only checks the version.
https://docs.python.org/3/library/ensurepip.html
https://www.python.org/dev/peps/pep-0453/#updating-the-private-copy-of-pip
I'm updating some instructions for my students, in which the first thing I
do is have them run ensurepip:
$ python3 -m ensurepip --upgrade
which resulted in:
$ python3 -m ensurepip --upgrade
Looking in links:
/var/folders/ym/tj87fc850yd6526nbrn14rxmgn/T/tmpwc8nd6oj
Requirement already
> On Aug 4, 2018, at 5:36 AM, Nick Coghlan wrote:
>
> I don't think there are any predefined helpers in fpm for that kind of
> model though, so you'd likely need some additional automation around
> setting up auto-generation of certbot-plugin packages (whereas certbot
> itself could likely use
On 2018-08-06 19:49, Chris Jerdonek wrote:
Does this proposal mean that .pyc files would need to be regenerated
after installing from a wheel (because the timestamp inside the .pyc
file would no longer match the .py file from which it came)?
No, I specifically mentioned that the timestamps of
Does this proposal mean that .pyc files would need to be regenerated after
installing from a wheel (because the timestamp inside the .pyc file would
no longer match the .py file from which it came)? I could be wrong, but it
seems like it’s a desirable feature that .pyc files be generated and up to
Proposal: change timestamps of files installed from a wheel to the time
of installation, except for .py files.
**Existing situation**
Let's consider two ways of installing a Python package: installation
from a source tarball and installation from a wheel, in both cases using
"pip install".
