Open KabirDubey opened 4 weeks ago
Another .mise.toml
file configuration with no environment variables does not work either. I locally install python version 3.10.14 with mise use python@3.10
and only write
[tools]
python = {version = '3.10', virtualenv = '.venv'}
but this gives
mise no venv found at: ~/repos/test/.venv
To create a virtualenv manually, run:
python -m venv ~/repos/test/.venv
I expected .venv
to be automatically created. I can create and activate .venv
manually and it all works fine.
Another
.mise.toml
file configuration with no environment variables does not work either. I locally install python version 3.10.14 withmise use python@3.10
and only write[tools] python = {version = '3.10', virtualenv = '.venv'}
Nevermind--adding a line
[tools]
python = {version='3.10', virtualenv='.venv'}
[env]
_.python.venv = { path = ".venv", create = true } # create the venv if it doesn't exist
automatically creates the .venv
directory. This is a temporary solution; I assume that activating it is supposed to be manual. If you access the path with the key like this
[tools]
python = '3.10'
[env]
_.python.venv = ".venv"
_.python.venv = { path = ".venv", create = true } # create the venv if it doesn't exist
it's still seen as a duplicate.
(first time user)
Describe the bug I'm unable to configure my
.mise.toml
file to enable automatic virtual environment activation in my python project directory. Any action in mytest
directory, which solely consists of my.mise.toml
file, returns the following error:To Reproduce Get started:
mise
using Homebrew.~/.zprofile
(as opposed to~/.zshrc
)Configure python version management:
test
directory as a test projectnvim .mise.toml
and paste this example from the documentation:Expected behavior I expect a python virtual environment to be automatically created and activated.
mise doctor
output