pixi-pack 0.3.2 does not support pyproject.toml in certain scenarios

[dennis-wey]

For me pixi-pack stopped working with version 0.3.2.
I'm using a pyproject.toml as manifest, here is a reduced example:

[project]
name = "pixi-test"
requires-python = ">= 3.12"
dynamic = ['version']

[tool.pixi.project]
channels = ["conda-forge"]
platforms = ["osx-arm64", "linux-64"]

[tool.pixi.feature.prod.dependencies]
pydantic = "*"

[tool.pixi.feature.prod.pypi-dependencies]
pixi_test = { path = ".", editable = true }

[tool.pixi.feature.actions.dependencies]
pixi-pack = "*"

[tool.pixi.environments]
prod = ["prod"]
actions = ["actions"]

calling

pixi run --environment actions pixi-pack pack --environment prod --platform linux-64 --ignore-pypi-errors

results in

/Users/denniswayland/ghq/github.com/BY-Product-Development/plan-lde-ui-backend/pixi-test/pixi.toml

This only occured when using pixi-pack version 0.3.2. It's working with 0.3.1

[delsner]

With #94 pixi-pack now requires passing the path to the manifest file or its parent directory. If you don't pass anything, the current default is $PWD/pixi.toml. So you can use one of the two following commands:

$ pixi run --environment actions pixi-pack pack --environment prod --platform linux-64 --ignore-pypi-errors pyproject.toml
$ pixi run --environment actions pixi-pack pack --environment prod --platform linux-64 --ignore-pypi-errors .

I've changed the default to $PWD in #99; after the PR is merged, your command will also work again.

[dennis-wey]

Thanks! I wasn't aware that we can also directly specify the manifest. In that case I'll change it to your recommendation.