Replies: 3 comments
-
I'm a bit busy at the moment but it might be worth glancing at the code for this and seeing if I missed something obvious: Lines 460 to 500 in d7f64e2 |
Beta Was this translation helpful? Give feedback.
-
I've analyzed all configuration sequence declarations and seem to have found inconsistencies that lead to unexpected behavior: I took 3 sources: Then have brought them to a single format and sorting order for ease of comparison, after which, divided them into logical groups:
Then take configuration order from Configuration doc as order reference and began to compare. |
Beta Was this translation helpful? Give feedback.
-
Partially fixed here |
Beta Was this translation helpful? Give feedback.
-
Hello! I tried to use the
Profiles
feature based on doc and didn't understand which env-dependent files I could use:It is clearly stated at the beginning of the document:
So for now I think I can only use one type of paths:
.mise.{MISE_ENV}.toml
But below we can see the priority list, which contains many more paths depending on MISE_ENV:
And when I tried to use
.mise/config.{MISE_ENV}.toml
ormise/config.{MISE_ENV}.toml
it didn't have any effect:(this is my project preferred structure)
I created a small example to reproduce what I want, where:
CI Environment: should use homebrew python 3.12
Dev Environment: should install python 3.10
p.s. Python versions different to test the
MISE_ENV
call usingpython3 --version
Example with
mise/config.{MISE_ENV}.toml
- doesn't workAs you can see, the Python version is the same and equal to the Python homebrew version.
Example with
.mise.{MISE_ENV}.toml
- workHere dev python is 3.10 and ci is 3.12, just like we wanted
So my question is: where is the problem here?
P.S. I'm glad the configuration from root works, but I'd just like to use other methods if it's legal.
Beta Was this translation helpful? Give feedback.
All reactions