How are nested .tool-versions treated?

[airtonix]

using this structure

home/
  test.sh
  .tool-versions
  project/
    .tool-versions
    sub-project/
      .tool-versions 

Will this be true?

cat .tool-versions
# python 3.12.5

python --version
# Python 3.12.5

cd project
cat .tool-versions
# python 3.10.10

python --version
# Python 3.10.10

cd sub-project
cat .tool-versions
# python 2.73.0

python --version
# Python 2.73.0



cd ..
cat .tool-versions
# python 3.10.10

python --version
# Python 3.10.10

cd /

cat .tool-versions
cat: .tool-versions: No such file or directory

python --version
# I suspect vfox will incorrectly report "Python 3.10.10" when it should report what ever the system (dnf/apt/pkg) installed version

Mise also has this problem since it is env based.

Shims while they are a few milliseconds slower mean that they are accurate.

Another interesting problem with the PATH manipulation approach:

command_that_expects_to_use_python_three_ten() {
   cd project/
   # some python command that only works on 3.10 +
   sleep 10

   # some python command that only works on 3.10 +
   sleep 10

   # some python command that only works on 3.10 +
   sleep 10

   # some python command that only works on 3.10 +
   sleep 10
}

command_that_expects_to_use_python_two_seven(){
   cd project/sub_project/

   # some python command that only works on python 2.7 - 2.9
   sleep 10

   # some python command that only works on python 2.7 - 2.9
   sleep 10
}


# run them in parallel
command_that_expects_to_use_python_three_ten &
command_that_expects_to_use_python_two_seven &

this will fail because the second one will cause the PATH to point at the incorrect version of python