Open m0lson84 opened 1 week ago
this is a feature request, you can't use env vars like that in the field
Understood that I can't use ${XDG_CONFIG_HOME}
in the config.toml
, but I am still seeing a difference in overriding the configuration of the Python plugin compared to the others that I'm using (go and node). I've updated my config to use absolute paths (showing ~
to denote home dir).
[tools]
go = "1.23"
node = "lts"
python = "3.13"
[settings]
env_file = ".env"
experimental = true
go_default_packages_file = "~/.config/mise/golang"
[settings.python]
default_packages_file = "~/.config/mise/python"
This is the relevant portions from mise doctor
:
toolset:
go@1.23.2
node@20.18.0
python@3.13.0
env_vars:
MISE_ENV_FILE=.env
MISE_NODE_DEFAULT_PACKAGES_FILE=~/.config/mise/nodejs
MISE_SHELL=zsh
settings:
go_default_packages_file = "~/.config/mise/golang"
python_default_packages_file = "~/.default-python-packages"
[python]
default_packages_file = "~/.default-python-packages"
I would expect to see both python_default_packages_file
and python.default_packages_file
to be the value provided in my config.toml
.
I'm very much a noob when it comes to Rust, but I'd be happy to try my hand at creating a PR for this to gain more experience if that would be okay.
Describe the bug
When installing a new version of Python the
python.default_packages_file
setting does not seem to be used to fine the path to the default packages file. This seems to be the case for both the TOML setting and environment variable.To Reproduce
python.default_packages_file
setting to the same path.Expected behavior
Expect the overridden default packages file path to be used when installing a new Python version.
Contents of
config.toml
mise doctor
output