-
Notifications
You must be signed in to change notification settings - Fork 19
fix: if a spec is source, don't merge but force the source #405
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: if a spec is source, don't merge but force the source #405
Conversation
@ruben-arts not sure what's happening here but do we need to "merge" any specs at all? Or is this when there is a source spec and another spec at the same time (in which case we should ignore everything except the source one?). |
assert "contains spaces" in str(exc) | ||
|
||
|
||
def test_specs_with_none(): |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
can we maybe add a test with source usecase?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I added one
…s_on_merge # Conflicts: # backends/pixi-build-ros/pixi.lock
This is failing due to not having the latest |
"py_rattler", | ||
"py-pixi-build-backend", | ||
# TODO: publish to pypi | ||
# "py-pixi-build-backend", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I wonder if it should be also lowercase like py_rattler?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
the conda-forge
maintainers asked me to use -
s
Fixes #399
Tested with the example in https://github.com/noahjutz/robostack-build-local-package-issue-minimal/tree/main, thanks @noahjutz for this!
We just took the
binary_spec
but if it's source, that will property returnsNone
, resulting in the error from the issue. This change deals with that by forcing a dependency from source to be only from source, skipping the merge code.If in the future this code would be reached, we now do type checking to avoid this strange error.