Fix an infinite recursion due to setuptools and setuptools-scm #744
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.
There is a bootstrapping issue when trying to build
setuptool-scm
, since building it (transitively) requiressetuptools-scm
itself. The same holds forsetuptools
. This "fixes" that by removing any references tosetuptools
andsetuptools-scm
from the entries gathered frompoetry.lock
with the idea that we should default tosetuptools
andsetuptools-scm
from nixpkgs.This fixes #648, albeit quite ugly.
A better approach would be to build the versions of
setuptools
andsetuptools-scm
specified inpoetry.lock
using whateversetuptools
andsetuptools-scm
is in nixpkgs, and usesetuptools
andsetuptools-scm
frompoetry.lock
afterwards. However, I'm not sure how to best go about this, since it would require a separate Python environment.