Add failing test for conda/pip conflict #569
Draft
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
✅ Deploy Preview for conda-lock ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
maresb
force-pushed
the
conda-pip-conflict
branch
from
a7eb669
to
e60309c
Compare
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.
Added @jamesmyatt's environment file as a failing test from #540 (comment).
I'd really like to know the veracity of the following assertion at the end of
conda_lock.lockfile.v2prelim.models.Lockfile._toposort:Running this test in the debugger, the assertion holds, and
dep.manager != manageris never triggered. (It's also currently not triggered by anything in the test suite. 😢)I expect that figuring out the right thing to do here and fixing it will involve quite a deep dive.