Error importing BAR_TYPES with new pip 22.1 release

[kabirkhan]

pip-tools breaks with the new version of pip "22.1". Error:

ImportError: cannot import name 'BAR_TYPES' from 'pip._internal.cli.progress_bars' (/tmp/tmpxfal9pqx/6297f3abdc8a9aff/test-env/lib/python3.9/site-packages/pip/_internal/cli/progress_bars.py)

Environment Versions

OS: Ubuntu 20.04
Python version: 3.9
pip version: 22.1
pip-tools version: 6.6.0

Steps to replicate

1. pip install -U pip pip-tools
2. pip-compile requirements.in

Expected result

Compilation is successful

Actual result

Full traceback from my CI job.

Traceback (most recent call last):
  File "/tmp/tmpxfal9pqx/6297f3abdc8a9aff/test-env/bin/pip-compile", line 5, in <module>
    from piptools.scripts.compile import cli
  File "/tmp/tmpxfal9pqx/6297f3abdc8a9aff/test-env/lib/python3.9/site-packages/piptools/scripts/compile.py", line 21, in <module>
    from ..repositories import LocalRequirementsRepository, PyPIRepository
  File "/tmp/tmpxfal9pqx/6297f3abdc8a9aff/test-env/lib/python3.9/site-packages/piptools/repositories/__init__.py", line 1, in <module>
    from .local import LocalRequirementsRepository
  File "/tmp/tmpxfal9pqx/6297f3abdc8a9aff/test-env/lib/python3.9/site-packages/piptools/repositories/local.py", line 14, in <module>
    from .pypi import PyPIRepository
  File "/tmp/tmpxfal9pqx/6297f3abdc8a9aff/test-env/lib/python3.9/site-packages/piptools/repositories/pypi.py", line 23, in <module>
    from pip._internal.cli.progress_bars import BAR_TYPES
ImportError: cannot import name 'BAR_TYPES' from 'pip._internal.cli.progress_bars' (/tmp/tmpxfal9pqx/6297f3abdc8a9aff/test-env/lib/python3.9/site-packages/pip/_internal/cli/progress_bars.py)

[jason-nance]

Looks like BAR_TYPES was removed in this commit.

[AndydeCleyre]

There's a fix for this in the new resolver PR, and we either need pull that bit out for a more immediate release, or finalize and merge that PR, which still has at least one problem.

[klimburg]

Just hit this in our CI

[pradyunsg]

Pulling that out into a more immediate release seems reasonable to me. :)

[lafolle]

For now i am just pinning pip to 22.0.4. Looking forward to the fix!

[AndydeCleyre]

I can't be at a computer for a little while, @atugushev want to do a small release soon?

[deifactor]

IIRC this isn't the first time a new pip release has broken pip-tools. Would it be a good idea to have upper bounds in its dependency?

[wizpig64]

That commit has been in the pip main branch for a month. ideally, this repo should be testing against that regularly to catch for this kind of thing early, rather than needing to add a version cap that would just get in the way later.

oh dear, it does regularly check for this: https://github.com/jazzband/pip-tools/runs/6267937837?check_suite_focus=true

edit: oh yeah, here's where the relevant discussion continues, back through this wormhole to January: #1558 (comment)

[BarnabasSzabolcs]

I'm a bit puzzled why pip and pip-tools are not kept within the same project.

pip-tools is instrumental to using pip since pip-compiles enables devs to separate direct dependencies from indirect ones. Also, it is great for fixing versions.
(it makes the pip system work just like packages.json and npm...)

[hugovk]

I'm a bit puzzled why pip and pip-tools are not kept within the same project.

This also came up the last quarter, so I'll repeat #1558 (comment):

I'm not sure whether a change in organisation would necessarily help, the pip team will continue to change their private internal functions as they need to (and there will be more changes to use Rich more for better output).

Also, the pip team are very busy working on pip and we can't expect them to maintain pip-tools as well.

In fact, moving pip-tools out of Jazzband would be a backwards step: it would mean that fewer people are able to maintain it.

---

As noted by @wizpig64 above, pip-tools does indeed have a daily cron regularly testing against pip's main branch, in fact it did catch the change in pip (but remember: pip has no official API) and started failing a month ago.

This also happened last quarter, so I'll also repeat #1558 (comment):

Wherever it lives, I'd suggest a closer eye is paid to the integration of pip with pip-tools, especially in the lead up to pip's quarterly releases. (And look out for the pip release issues for planned release dates e.g. pypa/pip#10726.)

[hugo2121-trip]

what was the fix there?
I got same issue with

pip version 22.1.2 (also tried 22.0.4)
pip-tools version 6.8.0

[AndydeCleyre]

@hugo2121-trip

Can you provide a reproducible procedure?

[hugovk]

Sorry I clicked the wrong button!

[hugo2121-trip]

@hugo2121-trip

Can you provide a reproducible procedure?

thanks for replying. I fixed the issue. My team is using tox to run some command, and seems tox using pip 22.1.2 under the hood.

I made some dependencies change to force using some version:

pip == 22.0.4
pip-tools==5.4.0

and fixed the issue.

[thehackermonkey]

For me it worked after doing:

1. pip install pip==22.0.4
2. pip install --upgrade pip-tools

Thanks to @lafolle for pointing the latest working version.

[kijewskimateusz]

EDIT: Have been using old version of PIP-Tools in Pre-Commit

[matheusft]

For me it worked after doing:

1. pip install pip==22.0.4
2. pip install --upgrade pip-tools

Thanks to @lafolle for pointing the latest working version.

That worked fine for me. Thanks =)