docs: add section on pinned package conflicts in conda and PyPI integration#5217
Merged
ruben-arts merged 1 commit intoprefix-dev:mainfrom Dec 30, 2025
Merged
docs: add section on pinned package conflicts in conda and PyPI integration#5217ruben-arts merged 1 commit intoprefix-dev:mainfrom
ruben-arts merged 1 commit intoprefix-dev:mainfrom
Conversation
…ration Add link to the docs in the error message.
ruben-arts
approved these changes
Dec 30, 2025
Contributor
ruben-arts
left a comment
There was a problem hiding this comment.
Thank you! This is a great helper!
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Description
I added a section explaining pinned package conflicts due to the two-staged solve with conda and pypi-dependencies.
Also, I added a link to the docs in the corresponding error message.
Motivation
I had to explain this error message to a colleague today, which seemed to imply that the package it was trying to install had two conflicting dependencies.
How Has This Been Tested?
I have not tested it locally, but corrected the corresponding test that checked that error message.
Checklist:
schema/model.py.