pip_and_pip_tools 7.6.1

Purpose

Occasionally, a new pip release is incompatible with the latest existing pip-tools release.

The purpose of this package is to make it easy to ensure compatible installations of the two tools.

Approach

Once the incompatible pip release hits, there may be a span of time during which pip-tools is not yet ready for its own release.

Upon or in advance of these events, this package will be swiftly published to PyPI, and will depend on:

• pip-tools>=LATEST

• pip<INCOMPATIBLE

This package will have no real content of its own.

Once a pip-tools version is released that is compatible with the latest pip release, this package will be published again, depending on:

• pip-tools>=LATEST

• pip

The pip-tools package itself sets the minimum pip version.

Warnings

This package is currently maintained by me, some guy you don’t know.

I am not going to anything malicious with this package, but depending on it without verifying its content is a risk you should beware.

Usage

$ pip install -U pip pip-tools pip-and-pip-tools

Maintenance

If anyone wants to take over maintenance of the package, or adopt it into a trusted organization, please open an issue.

Keeping it updated:

• Install and setup [mise](https://mise.jdx.dev/)

• Edit vars.json, and a hook defined in mise.toml should rewrite pyproject.toml. vars.json has three keys:

  • bad_pip_version: INCOMPATIBLE in the Approach section above, it’s either a pip version string to block updating to (or beyond), or the empty string when the latest pip release is compatible with pip-tools

  • latest_pip_tools_version: LATEST in the Approach section above, it’s a pip-tools minimum version string

  • Leave version_overflow set to the empty string unless you need a second release against the same pip-tools version, in which case use an integer string like "1".

• Commit, tag, and push, with the tag being the release version, for example:

$ git commit vars.json pyproject.toml -m "block pip 26.1"
$ git tag 7.6.0
$ git push && git push --tags