Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Sanity check pip in github workflow #1947

Merged
merged 1 commit into from
Mar 23, 2023
Merged

Sanity check pip in github workflow #1947

merged 1 commit into from
Mar 23, 2023

Conversation

bemoody
Copy link
Collaborator

@bemoody bemoody commented Mar 23, 2023

Installing packages using pip can break pip for weird reasons (see issue #1915).

Add a sanity check to catch seriously broken cases before they're merged. This may be unnecessary if we stop doing pip upgrades (see issue #1921 / pull #1939) but isn't a bad idea anyway.

Since pip itself uses the Python interpreter and Python libraries that
it installs, it's possible that installing packages using pip can
break pip and make it impossible to upgrade or downgrade packages
afterwards.

As a simple sanity check, try invoking the "freeze" command after
installing the packages.  This should catch some blatant conflicts
(such as a recent issue with the cryptography package) that make pip
completely non-functional.
@tompollard
Copy link
Member

thanks, looks good to me!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants