Upgrade setuptools to 72.1.0 to resolve installation error #1338
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
1 task
|
👋 Hi @yogeshojha, |
yogeshojha
deleted the
1336-bug-docker-not-building-pip-failing-modulenotfounderror-no-module-named-setuptoolscommandtest
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Our Docker build was failing due to an error with setuptools. Specifically, we encountered a
ModuleNotFoundError: No module named 'setuptools.command.test'. This was caused by issues with setuptools version 72.0.0, which was yanked from the repository by the package maintainers.We've updated our Dockerfile to explicitly install setuptools version 72.1.0. This version resolves the issues present in 72.0.0 and allows our build process to complete successfully.