We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
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.
pixi --version
pixi init --import environment-dev.yml
returns
❯ pixi init --import environment-dev.yml × Can't parse '-e .' as pypi dependency ╰─▶ Expected package name starting with an alphanumeric character, found `-` -e . ^
I have a environment-dev.yml file like
name: "myenv" channels: # internal packages - https://HIDDEN.jfrog.io/artifactory/api/conda/conda/dtn # conda-forge - https://HIDDEN.jfrog.io/artifactory/api/conda/conda - nodefaults dependencies: - python=3.12 - XXX - pip - -e .
Normally I run mamba env update -f environment-dev.yml. I guess this is the equivalent of mamba env create -f environment.yml & pip install -e
mamba env update -f environment-dev.yml
mamba env create -f environment.yml & pip install -e
It would be great for pixi init --import to handle this.
pixi init --import
Thanks, Ray
pixi init --import environment-dev.yml works as expected
The text was updated successfully, but these errors were encountered:
No branches or pull requests
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
returns
Issue description
I have a environment-dev.yml file like
Normally I run
mamba env update -f environment-dev.yml
. I guess this is the equivalent ofmamba env create -f environment.yml & pip install -e
It would be great for
pixi init --import
to handle this.Thanks,
Ray
Expected behavior
pixi init --import environment-dev.yml
works as expectedThe text was updated successfully, but these errors were encountered: