Disable build isolation for dependencies [DO NOT MERGE - CI test] #872
+1
−1
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.
This should help resolve mismatch in versions during CI runs. With build isolation, when dependencies are built a new venv is created for every dependency. This by itself is not a problem, the problem is that it also installs build requirements that are significantly newer than the rest of the system. This often creates errors because newer setuptools refuse to use their vendored dependencies and the system ones are preferred.