Closed storymode7 closed 3 years ago
Why was this change necessary?
Upgrading pip
Pip version used in virtualenv is associated with python version, and older python versions end up using outdated pip that came packaged with it.
This results in a failure when installing some packages like cryptography
cryptography
Installing wheel: Updated standard for python packaging.
Without wheel a few packages have to fallback on setup.py, throwing this message:
setup.py
Using legacy 'setup.py install' for pkg-name, since package 'wheel' is not installed.
Wheel is also safer than setup.py and faster Source: https://www.python.org/dev/peps/pep-0427/#rationale
How does it address the problem?
Upgrades pip and installs wheel before any installation begins when doing make install
make install
Are there any side effects?
None
Upgrading pip
Pip version used in virtualenv is associated with python version, and older python versions end up using outdated pip that came packaged with it.
This results in a failure when installing some packages like
cryptographyInstalling wheel: Updated standard for python packaging.
Without wheel a few packages have to fallback on
setup.py, throwing this message:Wheel is also safer than setup.py and faster Source: https://www.python.org/dev/peps/pep-0427/#rationale
Upgrades pip and installs wheel before any installation begins when doing
make installNone