Update pip to 20.2.2, setuptools to 49.6.0

[mkoeppe]

Previous update: #29803 (20.1.1, 47.1.1)

• https://pypi.org/project/pip 20.2.2 was released 2020-08-11 and is latest as of 2020-08-27.

• setuptools 49.6.0 was released on 2020-08-13 and is latest stable as of 2020-08-27. (50.0.0 will bring backward-incompatible changes; see https://setuptools.readthedocs.io/en/latest/history.html#v50-0-0)

CC: @jhpalmieri @dimpase

Component: packages: standard

Author: Matthias Koeppe

Branch: 51eac01

Reviewer: John Palmieri

Issue created by migration from https://trac.sagemath.org/ticket/30317

[mkoeppe]

Branch: u/mkoeppe/update_pip_to_20_2_1__setuptools_to_49_2_1

[mkoeppe]

Author: Matthias Koeppe

[mkoeppe]

Commit: 91f21f6

[mkoeppe]

New commits:

a22b6ae	build/pkgs/pip: Update to 20.2.1
91f21f6	build/pkgs/setuptools: Update to 49.2.1

[sagetrac-git]

Changed commit from 91f21f6 to eded6be

[sagetrac-git]

Branch pushed to git repo; I updated commit sha1. New commits:

eded6be

build/pkgs/pip: Update to 20.2.2

[sagetrac-git]

Branch pushed to git repo; I updated commit sha1. New commits:

51eac01

build/pkgs/setuptools: Update to 49.6.0

[sagetrac-git]

Changed commit from eded6be to 51eac01

[tobiasdiez]

comment:7

I tried this as recommended in #30459, but it fails with "Error downloading pip-20.2.2.tar.gz" because this version of pip cannot be found on any of the sage mirrors apparently. Do I have to change something before running this branch?

Just out of interest, what is the reason for this spkg infrastructure over say pipenv + pipfile?

[mkoeppe]

comment:8

Replying to @tobiasdiez:

I tried this as recommended in #30459, but it fails with "Error downloading pip-20.2.2.tar.gz" because this version of pip cannot be found on any of the sage mirrors apparently. Do I have to change something before running this branch?

Tickets with package changes need ./configure --enable-download-from-upstream-url until the ticket has been merged into the next beta (which is when the release manager uploads the tarballs to the mirrors).

[mkoeppe]

comment:9

Replying to @tobiasdiez:

Just out of interest, what is the reason for this spkg infrastructure over say pipenv + pipfile?

If you are asking why we bypass proper package management by pip and install things in the most basic way using pip --ignore-installed --verbose --no-deps --no-index (see build/bin/sage-pip-install)... let's just say that it is the result of design decisions made a long time ago based on implementation constraints that were valid at that time - but no longer bind us now.

I am hoping that we can make the installation of Python packages more straightforward in the Sage 9.3 cycle. #29500 (Install all Python packages via pip wheel) is a step in this direction.

I haven't looked at pipenv in detail; pipfile looks like it is far from a stable version

[tobiasdiez]

comment:10

After configure it downloaded pip. However, the installation failed with the same error as reported in #30459. I also tried to add with_pip=True in the constructor argument of EnvBuilder in sage-venv, but this script doesn't seem to be triggered at all during a make.

Thanks for the explanation. It's interesting to learn more about the inner workings of sage. Pipfile is as stable as pipenv, since the latter uses it heavily. But if I understand it correctly, you are not using a virtual environment for the local python installation, right?

[jhpalmieri]

comment:12

Looks like a straightforward update to me. It works for me on OS X. Other issues could be addressed on another ticket: the problems reported by @tobiasdiez look like they're independent of the changes here, unless I'm misunderstanding.

[jhpalmieri]

Reviewer: John Palmieri

[mkoeppe]

comment:13

Thanks!

[vbraun]

Changed branch from u/mkoeppe/update_pip_to_20_2_1__setuptools_to_49_2_1 to 51eac01

[slel]

Changed commit from 51eac01 to none

[slel]

comment:15

50.0.0 will bring backward-incompatible changes;
see ​https://setuptools.readthedocs.io/en/latest/history.html#v50-0-0

Some if not all these changes are reverted in 50.1.0, 50.2.0, 50.3.0,
see history.