You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Whenever I change a version in my Python project I get issues with stale versions being cached somewhere. Stuff like this:
(.venv) $ pixi install
Error: × failed to solve the pypi requirements of 'default' 'linux-64'
├─▶ failed to resolve pypi dependencies
╰─▶ Because rayforge==0.24.post3+git.b6c16603.dirty depends on pycairo==1.27.0 and pycairo==1.28.0, we can conclude that rayforge==0.24.post3+git.b6c16603.dirty cannot be used.
And because only rayforge==0.24.post3+git.b6c16603.dirty is available and you require rayforge, we can conclude that your requirements are unsatisfiable.
Except that Version "1.27.0" is not defined anywhere in my entire project:
then "pixi install" passes. I made sure that all requirements from requirement.txt are synced up with the versions specified in Pixi. (I have to maintain both in parallel because the package is shipped as a wheel.)
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Whenever I change a version in my Python project I get issues with stale versions being cached somewhere. Stuff like this:
Except that Version "1.27.0" is not defined anywhere in my entire project:
Any idea what I am doing wrong? When I temporarily comment out my package reference:
then "pixi install" passes. I made sure that all requirements from requirement.txt are synced up with the versions specified in Pixi. (I have to maintain both in parallel because the package is shipped as a wheel.)
How can this be resolved?
Beta Was this translation helpful? Give feedback.
All reactions