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

Fix for inclusion of setuptools in the lock and install phase + other BAD_PACKAGES. #5231

Merged
merged 2 commits into from
Aug 8, 2022

Conversation

matteius
Copy link
Member

@matteius matteius commented Aug 7, 2022

After switching to use exclusively vendor'd pip for remaining commands, which includes install, two of the tests when run on python < 3.10 were failing in a weird loop where setuptools would get uninstalled and then be requested to install the newer version of setuptools and fail. I am not sure why this passed on python 3.10 or why its so problematic for versions less than 3.10.

The other thing this should fix is pipenv should no longer include BAD_PACKAGES in the Pipfile.lock -- these are packages that were already required be installed when installing pipenv so it should not be necessary to include them in the lock. I had to manually delete setuptools from the pipenv Pipfile.lock to get the build to even run the tests for python versions < 3.10 in this PR: #5229

@matteius matteius requested a review from oz123 August 8, 2022 12:15
@oz123 oz123 merged commit 720c1ed into main Aug 8, 2022
@oz123 oz123 deleted the ignore-bad-packages-from-install branch August 8, 2022 12:21
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