Closed tumidi closed 4 months ago
I'd expect $POE_ROOT/$POE_PWD variables to get expanded in [tool.poe.env].
$POE_ROOT
$POE_PWD
[tool.poe.env]
[tool.poe.env] GLOBAL_POE_ROOT = "${POE_ROOT}" # doesn't work [tool.poe.tasks.my-task] default_item_type = "cmd" sequence = [ "echo GLOBAL_POE_ROOT=${GLOBAL_POE_ROOT}", "echo TASK_POE_ROOT=${TASK_POE_ROOT}", ] [tool.poe.tasks.my-task.env] TASK_POE_ROOT = "${POE_ROOT}" # works
I created a minimal reproduction: https://github.com/tumidi/poethepoet-env-test
Output is:
$ poe my-task GLOBAL_POE_ROOT= TASK_POE_ROOT=/tmp/poethepoet-env-test
Hi @tumidi, yes I would expect that too. Thanks for reporting this.
This was incidentally fixed by the recent refactor of config management that is now on the development branch.
This issue is now fixed with 0.26.0 🚀
I'd expect
$POE_ROOT
/$POE_PWD
variables to get expanded in[tool.poe.env]
.I created a minimal reproduction: https://github.com/tumidi/poethepoet-env-test
Output is: