`conda run --name env_name file.py` does not work

[matte-esse]

When I click cmd+R on a python file

conda run --name env_name file.py

Appears in my terminal. But then the environment clearly isn't activated because it fails to import packages that are in that environment. As you can see below

(bf) ➜  bagflow git:(main) ✗ python file.py
here
(bf) ➜  bagflow git:(main) ✗ conda run --name bf python file.py
Traceback (most recent call last):
  File "file.py", line 1, in <module>
    import pytest
ModuleNotFoundError: No module named 'pytest'

ERROR conda.cli.main_run:execute(49): `conda run python file.py` failed. (See above for error)

This is on a Apple Silicon Mac using miniconda

[karthiknadig]

@matte-esse Can you confirm that the env bm has pytest?

[matte-esse]

Yes. You can also see that bf (not bm) has pytest from my terminal output. when I simply type python file.py the env bf is used and the file runs.

Honestly the whole systems feels very redudant. Once I select the interpreter the environment is activated any time a terminal panel is initiated so the environement does not need to be specified. cmd+R can just me mapped to python file.py it would be much cleaner.

Even now that I disabled the extension Python Environments it still uses absolute path to both python and the file

/Users/matt/miniconda3/envs/bf/bin/python /Users/matt/Documents/create_test_project.py

Now it works so no big deal but I would like this better in my terminal

python create_test_project.py

[karthiknadig]

@matte-esse thanks for the details, One another question, are you using the stable or the pre-release of the python environments extension? There was a fix for this in pre-release.

[matte-esse]

yes I just switched to pre-released and it works now. I guess next time I'll do that before I post.

Then I suggest switching to this easier to read command when vs code knows that the right environment is already activates

python create_test_project.py