Update pip to 20.0.2
ClosedPublic
Actions

Authored by jwinnie on Jan 27 2020, 1:24 AM.

Details

Reviewers

DataDrake

Group Reviewers

Triage Team

Commits

R2440:8519a0af24dc: Update pip to 20.0.2

Summary

The new version of pip includes many bug-fixes, internal improvements, and an improved command-line interface.

The --user option is now assumed when pip is run without root privileges.
An option --no-python-version-warning has been added to silence warnings related to deprecation of Python versions.
The ~ prefix is now expanded to represent the user directory in path options, configs, and environment variables.
setup.py-based builds that do not generate an .egg-info directory are now deprecated.
The --skip-requirements-regex option has been removed.
The passing of install-location-related options via --install-option has been deprecated.
Wheel processing no longer permits wheels containing more than one top-level .dist-info directory.

Signed-off-by: Jeremy Potter <solus@stormdesign.us>

Test Plan

I ran pip install --user pipenv and then pip uninstall pipenv as a test and there were no errors or issues detected.

Diff Detail

Repository

R2440 pip

Lint

Lint Not Applicable

Unit

Tests Not Applicable

Event Timeline

jwinnie created this revision.Jan 27 2020, 1:24 AM

Herald added a reviewer: Triage Team. · View Herald TranscriptJan 27 2020, 1:24 AM

jwinnie requested review of this revision.Jan 27 2020, 1:24 AM

jwinnie edited the summary of this revision. (Show Details)Jan 27 2020, 1:27 AM

jwinnie added a subscriber: YakoYakoYokuYoku.

Your Summary will be used by eopkg and Software Center as part of the Changelog. With the way it is written right now, it is factually incorrect and has unnecessary commentary. We are exactly 3 revisions behind, and are intentionally holding back pip 20 until after the Python 3.7 upgrade. The Summary is intended to be a discussion of what has changed, not why it was changed (unless patches are involved) nor what wasn't changed.

This revision now requires changes to proceed.Jan 27 2020, 1:31 AM

@DataDrake, is this changelog fine?

jwinnie edited the summary of this revision. (Show Details)Jan 27 2020, 3:00 AM

Albeit posting portions of the change-logs from the sources is a good way to describe what happened between versions, this is only useful if you only put info like a few of the features the newer versions introduce. With bug-fixes I'd recommend to put that bugs were fixed. For changes in documentation we generally ignore them if the documentation of the package is found online. If lots of changes were added we put a link to the change-log.

A more adequate summary could be in this form:

The new version of <package> includes bug-fixes and the following changes:
- Feature n1
- Feature n2
- Feature n3
- (A few features worth highlighting)

Signed-off-by: Your name <your@email.com>

Also after each update of a package and package rebuild we bump the number of the release.