Closed pavelzw closed 1 month ago
I've found this to be wrong as well.
I was lately thinking of making the pixi init
a more interactive tool. Allowing all settings to be set through cli as well. And possibly giving some tips.
e.g.
$ pixi init
Setting up a pixi project:
1. Which manifest format do you want to use?
> `pixi.toml`
- `pyproject.toml`
2. Do you want to use "folder name" as the project name? (enter for yes/ input other name for no)
3. Which platforms is your project going to support?
[x] your platform
[ ] linux-64
[ ] osx-64
[ ] etc
4. Possibly more options....
Created the following content for you:
<cat of the added information to the manifest>
Next steps:
- Add packages with `pixi add`
- Run tasks in the environment with `pixi run`
- Add tasks with `pixi task add [name] [command]`
- More info in our documentation: https://pixi.sh
Checks
[X] I have checked that this issue has not already been reported.
[X] I have confirmed this bug exists on the latest version of pixi, using
pixi --version
.Reproducible example
Issue description
When executing
pixi init
, pixi doesn't create apixi.toml
but instead writes topyproject.toml
, even if I didn't specify it via--pyproject
. I personally like to keep my pyproject.toml and pixi.toml configuration separate as I can ensure that I don't use pixi's pip functionality this way.Expected behavior
I would expect that pixi always creates a
pixi.toml
and only adds topyproject.toml
if specified via--pyproject
. Alternatively, we could interactively prompt the user whether they want to have their pixi configuration inpixi.toml
orpyproject.toml
.