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
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
pick any python project on github whose version in setup.py must be manually updated
clone and fork a new branch
add a line # hello world! to __init__.py or some other file that will get installed by pip
push the new branch
Verify that pip install git+https://github.com/yourname/yourproject.git@yourrev still reports the latest published version; e.g. there's no auto version bump on each git commit
inspect pixi.lock and observe that it correctly points to your git fork
pixi run <something>
inspect .pixi/envs/yourenv/lib/python3.13/site-packages/yourproject/ and open the file you marked with the hello world. Observe that the change is not there.
Issue description
My pyproject.toml:
[tool.pixi.pypi-dependencies]
# DNM main plus #205, #207, #211
array-api-compat = { git = "https://github.com/crusaderky/array-api-compat.git", rev = "9761bf2c2790416e3c117ed9f64407525b4a3498" }
After I run pixi update, pixi.lock correctly points to my desired git fork:
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
# hello world!
to__init__.py
or some other file that will get installed by pippip install git+https://github.com/yourname/yourproject.git@yourrev
still reports the latest published version; e.g. there's no auto version bump on each git commitpixi update
pixi run <something>
.pixi/envs/yourenv/lib/python3.13/site-packages/yourproject/
and open the file you marked with thehello world
. Observe that the change is not there.Issue description
My pyproject.toml:
After I run
pixi update
,pixi.lock
correctly points to my desired git fork:However,
.pixi/envs/tests/lib/python3.13/site-packages/array_api_compat
contains the latest published version of the package on pypi.The problem was that the package above has a manually-updated version in setup.py, which hadn't been changed since the latest release on pypi.
Workaround
Manually update the version in your git tip's setup.py / setup.cfg / pyproject.toml to be higher than the latest released version
Expected behavior
pixi should respect my pyproject.toml, and should definitely respect its own pixi.lock.
The text was updated successfully, but these errors were encountered: