Update to 24.2, use pip source to install itself

[jjhelmus]

pip 24.2

Destination channel: defaults

Links

• PKG-5148
• Upstream repository
• Upstream changelog/diff
• Relevant dependency PRs:

Explanation of changes:

• Update to version 24.2
• Use the pip source to install itself. Note that setup.py was removed in version 24.1 so is no longer an option.
• Tracks similar changes in conda-forge:
  • Update to 24.1.2, use pip source to install itself. conda-forge/pip-feedstock#121
  • Update to 24.2, add setuptools and wheel as run dependencies conda-forge/pip-feedstock#125

[anaconda-pkg-build]

Linter check found the following problems:

ERROR conda.cli.main_run:execute(125): `conda run conda-lint /tmp/abs_adjh1sd0y5/clone` failed. (See above for error) The following problems have been found:

===== ERRORS =====

• clone/recipe/build.sh:3: pip_install_args: pip install should be run with --no-deps and --no-build-isolation.
• clone/recipe/meta.yaml:39: invalid_url: https://pip.pypa.io : Not reachable: 403
• clone/recipe/meta.yaml:48: invalid_url: https://pip.pypa.io : Not reachable: 403
  ===== Final Report: =====
  3 Errors and 0 Warnings were found

[anaconda-pkg-build]

Linter check found the following problems:

ERROR conda.cli.main_run:execute(125): `conda run conda-lint /tmp/abs_f61sopcfw2/clone` failed. (See above for error) The following problems have been found:

===== ERRORS =====

• clone/recipe/meta.yaml:48: invalid_url: https://pip.pypa.io : Not reachable: 403
• clone/recipe/meta.yaml:39: invalid_url: https://pip.pypa.io : Not reachable: 403
  ===== Final Report: =====
  2 Errors and 0 Warnings were found

[anaconda-pkg-build]

Linter check found the following problems:

ERROR conda.cli.main_run:execute(125): `conda run conda-lint /tmp/abs_cdxo1u_7uf/clone` failed. (See above for error) The following problems have been found:

===== ERRORS =====

• clone/recipe/meta.yaml:48: invalid_url: https://pip.pypa.io : Not reachable: 403
• clone/recipe/meta.yaml:39: invalid_url: https://pip.pypa.io : Not reachable: 403
  ===== Final Report: =====
  2 Errors and 0 Warnings were found

[dholth]

Neat!

[danpetry]

how does that work? the pip program is loaded into memory then the version in memory installs the version on disc?

[danpetry]

does that remove the need to set CONDA_ADD_PIP_AS_PYTHON_DEPENDENCY=0?

[JeanChristopheMorinPerso]

how does that work? the pip program is loaded into memory then the version in memory installs the version on disc?

Well, everything is always loaded in memory... What it does is just rely on the non-installed (so in-tree) pip to install itself. -m pip will call src/pip/__main__.py which is the CLI entrypoint.

[jjhelmus]

When importing packages, Python will search and load modules from various location on disk, such as from the site-packages directory. The PYTHONPATH variable can be use to add locations to the search path.

[jjhelmus]

does that remove the need to set CONDA_ADD_PIP_AS_PYTHON_DEPENDENCY=0?

No, CONDA_ADD_PIP_AS_PYTHON_DEPENDENCY prevents conda from installing the pip conda package when python is listed as a requirement in the recipe. The environment variable is the same as setting add_pip_as_python_dependency: false in .condarc.

[JeanChristopheMorinPerso]

Latest versions of pip requires python python>=3.8 AFAIK, see https://inspector.pypi.io/project/pip/24.2/packages/d4/55/90db48d85f7689ec6f81c0db0622d704306c5284850383c090e6c7195a5c/pip-24.2-py3-none-any.whl/pip-24.2.dist-info/METADATA#line.25. Should we also follow that?

[jjhelmus]

Latest versions of pip requires python python>=3.8 AFAIK, see https://inspector.pypi.io/project/pip/24.2/packages/d4/55/90db48d85f7689ec6f81c0db0622d704306c5284850383c090e6c7195a5c/pip-24.2-py3-none-any.whl/pip-24.2.dist-info/METADATA#line.25. Should we also follow that?

Yes. I bumped the minimum version for the build to 3.8.

[anaconda-pkg-build]

Linter check found the following problems:

ERROR conda.cli.main_run:execute(125): `conda run conda-lint /tmp/abs_94xk0pz503/clone` failed. (See above for error) The following problems have been found:

===== ERRORS =====

• clone/recipe/meta.yaml:39: invalid_url: https://pip.pypa.io : Not reachable: 403
• clone/recipe/meta.yaml:48: invalid_url: https://pip.pypa.io : Not reachable: 403
  ===== Final Report: =====
  2 Errors and 0 Warnings were found

[danpetry]

LGTM AFAICS. Do you need to build a couple of packages with it to make sure nothing untoward is happening? ("shouldn't" be, but in my experience bodies are buried in the distro and weird stuff can happen with build tools, we had an issue with this recently)

[anaconda-pkg-build]

Linter check found the following problems:

ERROR conda.cli.main_run:execute(125): `conda run conda-lint /tmp/abs_53xo6c8hgk/clone` failed. (See above for error) The following problems have been found:

===== ERRORS =====

• clone/recipe/meta.yaml:48: invalid_url: https://pip.pypa.io : Not reachable: 403
• clone/recipe/meta.yaml:39: invalid_url: https://pip.pypa.io : Not reachable: 403
  ===== Final Report: =====
  2 Errors and 0 Warnings were found

[danpetry]

Do you need to build a couple of packages with it to make sure nothing untoward is happening? ("shouldn't" be, but in my experience bodies are buried in the distro and weird stuff can happen with build tools, we had an issue with this recently)

FWIW: AnacondaRecipes/xgboost-feedstock#20

[JeanChristopheMorinPerso]

@danpetry I don't think it has to do with pip. Pip became more strict, but it's not a bug, it's a feature.

[danpetry]

looking more at the comment you made on xgboost, it's about a specific hatch hook which may not be used in all feedstocks, is that right? or even an implementation in the xgboost code which is very unlikely to appear in other feedstocks..?

[JeanChristopheMorinPerso]

Yes. It's going to be a problem for projects that set their own tags, which should be a low number of projects.