Skip to content
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

Open
blmaier opened this issue Dec 13, 2024 · 1 comment
Open

Support --manifest-path to project directory #2706

blmaier opened this issue Dec 13, 2024 · 1 comment
Labels
UX Related to the User Experience of pixi 👋 good first issue Good for newcomers 👩‍💻 cli Issue related to CLI

Comments

@blmaier
Copy link
Contributor

blmaier commented Dec 13, 2024

Problem description

The Pixi flag --manifest-path takes the path to a pixi.toml or pyproject.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:

$ pixi --version
pixi 0.39.2

$ pixi project --manifest-path myproj/pixi.toml name get
myproj

$ pixi project --manifest-path myproj/ name get
  × failed to read from file `myproj/`
  ╰─▶ Is a directory (os error 21)
@ruben-arts
Copy link
Contributor

This makes sense to me. We're open to PR's!

@ruben-arts 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 blmaier changed the title Support --manifest-path to project directory feat: Support --manifest-path to project directory Dec 17, 2024
@blmaier blmaier changed the title feat: Support --manifest-path to project directory Support --manifest-path to project directory Dec 17, 2024
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
Projects
None yet
Development

No branches or pull requests

2 participants