-
Notifications
You must be signed in to change notification settings - Fork 204
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
Support --manifest-path
to project directory
#2706
Labels
UX
Related to the User Experience of pixi
👋 good first issue
Good for newcomers
👩💻 cli
Issue related to CLI
Comments
This makes sense to me. We're open to PR's! |
ruben-arts
added
👋 good first issue
Good for newcomers
👩💻 cli
Issue related to CLI
UX
Related to the User Experience of pixi
labels
Dec 13, 2024
blmaier
added a commit
to blmaier/pixi
that referenced
this issue
Dec 16, 2024
Allow `pixi --manifest-path <path>` to accept a path to a project directory. This makes it easier to use pixi when scripting as the script does not need to know if a project is using pixi.toml or pyproject.toml. Implements: prefix-dev#2706
blmaier
added a commit
to blmaier/pixi
that referenced
this issue
Dec 16, 2024
Allow `pixi --manifest-path <path>` to accept a path to a project directory. This makes it easier to use pixi when scripting as the script does not need to know if a project is using pixi.toml or pyproject.toml. Implements: prefix-dev#2706
blmaier
added a commit
to blmaier/pixi
that referenced
this issue
Dec 16, 2024
Allow `pixi --manifest-path <path>` to accept a path to a project directory. This makes it easier to use pixi when scripting as the script does not need to know if a project is using pixi.toml or pyproject.toml. Implements: prefix-dev#2706
blmaier
changed the title
Support
feat: Support Dec 17, 2024
--manifest-path
to project directory--manifest-path
to project directory
blmaier
changed the title
feat: Support
Support Dec 17, 2024
--manifest-path
to project directory--manifest-path
to project directory
blmaier
added a commit
to blmaier/pixi
that referenced
this issue
Dec 18, 2024
Allow `pixi --manifest-path <path>` to accept a path to a project directory. This makes it easier to use pixi when scripting as the script does not need to know if a project is using pixi.toml or pyproject.toml. Implements: prefix-dev#2706
blmaier
added a commit
to blmaier/pixi
that referenced
this issue
Dec 21, 2024
Allow `pixi --manifest-path <path>` to accept a path to a project directory. This makes it easier to use pixi when scripting as the script does not need to know if a project is using pixi.toml or pyproject.toml. Implements: prefix-dev#2706
blmaier
added a commit
to blmaier/pixi
that referenced
this issue
Dec 23, 2024
Allow `pixi --manifest-path <path>` to accept a path to a project directory. This makes it easier to use pixi when scripting as the script does not need to know if a project is using pixi.toml or pyproject.toml. Implements: prefix-dev#2706
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
UX
Related to the User Experience of pixi
👋 good first issue
Good for newcomers
👩💻 cli
Issue related to CLI
Problem description
The Pixi flag
--manifest-path
takes the path to apixi.toml
orpyproject.toml
. This means the caller has to be aware which manifest file a project is using, and can make scripting more complicated. It would be convenient if the directory to the manifest could be used and Pixi would select the correct manifest file by the same logic it uses when manifest path isn't used.For example:
The text was updated successfully, but these errors were encountered: