Skip to content
This repository has been archived by the owner on Jan 8, 2023. It is now read-only.

Avoid using pip 2020-resolver #25

Merged
merged 1 commit into from
Nov 26, 2020

Conversation

ssbarnea
Copy link
Member

@ssbarnea ssbarnea commented Nov 26, 2020

It seams that our tox -e py36-devel is also affected by the endless loop install bug from the new pip resolver, we are forced to disable it, at least for this job.

This change also includes another temporary workaround for rich, which fails to install due to pip conflicts when switching to the old resolver.

Example: https://github.com/ansible-community/molecule-podman/pull/23/checks?check_run_id=1458663833
Related: pypa/pip#6536
Related: Textualize/rich#446

@ssbarnea ssbarnea added the bug This issue/PR relates to a bug. label Nov 26, 2020
It seams that our tox -e py36-devel is also affected by the endless
loop install bug from the new resolver, we are forced to disable it,
at least for this job.

Example: https://github.com/ansible-community/molecule-podman/pull/23/checks?check_run_id=1458663833
Related: pypa/pip#6536
Related: Textualize/rich#446
@ssbarnea ssbarnea merged commit f9cf02c into ansible-community:master Nov 26, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug This issue/PR relates to a bug.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant