-
Notifications
You must be signed in to change notification settings - Fork 222
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
pixi upgrade --dry-run
fails with "cannot update pypi dependencies"
#2770
Comments
I suppose this is related to Lines 1164 to 1185 in a343eef
|
I think this failure should be expected if one passes |
PR at gh-2771, which avoids the error observed here, while keeping these assertions passing: assert manifest_path.read_text() == manifest_content
assert lock_file_path.read_text() == lock_file_content The one that doesn't pass is: assert not os.path.exists(tmp_pixi_workspace / ".pixi") So the question is just whether that is acceptable for a dry-run in this situation, I suppose? |
Checks
I have checked that this issue has not already been reported.
I have confirmed this bug exists on the latest version of pixi, using
pixi --version
.Reproducible example
% pixi upgrade # works fine % pixi upgrade --dry-run × Cannot update pypi dependencies without first installing a conda prefix that includes python.
Issue description
dry run fails, but regular run succeeds
Expected behavior
behaviour should match the regular run
The text was updated successfully, but these errors were encountered: