Fix an issue with ubuntu, distutils, and pip #3437
Merged
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
The issue appears when doing 'pip install -e <package>', the package does not show up when doing 'pip freeze'. This is caused by Ubuntu installing a patched version of distutils (see pypa/distutils/issues/17 and pypa/setuptools/issues/3301; see also pypa/setuptools/issues/3625 for when this will stop working). This adds a workaround. Better would be to create a virtualenv and install into that and be insulated from odd OS upstream choices.
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.
The issue appears when doing 'pip install -e ', the package does not show up when doing 'pip freeze'. This is caused by Ubuntu installing a patched version of distutils (see pypa/distutils/issues/17 and pypa/setuptools/issues/3301; see also pypa/setuptools/issues/3625 for when this will stop working).
This adds a workaround. Better would be to create a virtualenv and install into that and be insulated from odd OS upstream choices.