Possible to force Python package install over conda package? #3550
Unanswered
matthewfeickert
asked this question in
Q&A
Replies: 1 comment
-
Currently the only way I know how to get around this is by making all tools that require the Git based Python project also be Python projects (i.e. [workspace]
authors = ["Matthew Feickert>"]
channels = ["conda-forge"]
name = "reproducer"
platforms = ["linux-64", "osx-arm64"]
version = "0.1.0"
[tasks]
[dependencies]
atlas-schema = ">=0.2.4,<0.3"
[feature.af.dependencies]
python = "==3.9.18"
[feature.af.pypi-dependencies]
atlas-schema = ">=0.2.4,<0.3"
awkward = { git = "git+https://github.com/scikit-hep/awkward.git", rev = "5e3849f385fcd1eab46358ab0ed5f0883bcd113b" }
[environments]
af = {features = ["af"], solve-group = "af", no-default-feature = true} $ rm -rf pixi.lock && pixi list -e af awkward
Environment: af
Package Version Build Size Kind Source
awkward 2.8.1 pypi git+https://github.com/scikit-hep/awkward.git?rev=5e3849f385fcd1eab46358ab0ed5f0883bcd113b#5e3849f385fcd1eab46358ab0ed5f0883bcd113b
awkward_cpp 45 pypi
dask_awkward 2025.3.0 pypi The "problem" here is that this then can potentially require huge amount of software to get installed as Python packages when it would be nice to have everything except the one piece of software you want installed from Git to be installed as conda packages. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
By default Pixi will work to prefer conda packages in an environment over Python (index) packages. However, there might be a time in an environment in your
workspace
that you want to get dependency as a Python package to test it at its current development state.Example:
rm -rf pixi.lock && pixi list -vv --environment af awkward:
results in
awkward
being installed as a conda package from conda-forge even though we specified that we wanted it to be installed from Git as a Python packagethis is happening because of the dependency structure of
atlas-schema
Is there a way to indicate that the Python package version of a package should take precedence and overwrite a conda package install?
cc @kratsg
Beta Was this translation helpful? Give feedback.
All reactions