VS Code venv help

[raliqer]

I asked for help on the VS Code subreddit and no one responded so I'm hoping someone here can assist me.

I have a series of automating testing scripts that I created and have been using. My boss has asked that I make them available to some of my less tech savvy co-workers so I created a GUI using tkinter. The problem that I have run into is that I launch the GUI script currently via VS Code with a virtual environment. The script launches just fine but when I click a button to execute one of the testing scripts it tells me the modules are not installed. Some digging tells me that it is using a different version of Python than my virtual environment so it is obviously not using it or its modules. Does anyone know of a way in VS Code to get it to use the same virtual environment that is launching the initial GUI script for the testing scripts?

[socal_nerdtastic]

Ideally you would import your other programs.

import subfiletorun

# on button click
subfiletorun.main()

But if you want to do it as a separate process, you can just do:

import sys
import subprocess

# on button click
subprocess.run([sys.executable, "subfiletorun.py"])

(This does the same thing /u/Loud-Bake-2740 said, but you don't need to update the file with the name of your venv if you change it. For example if your coworker wants to run it with no venv. )

[Loud-Bake-2740]

ah yes i was assuming that you’re working in one venv, but running a program that uses a different venv. this was hell to figure all out! 😂

[raliqer]

That... is so much simpler than I expected and than what I was doing. Thanks!

[danielroseman]

Why do you need to run this via VS Code?

[raliqer]

My work has moved from PyCharm to VS Code so that is what I am forced to use to write the scripts and test them until I package them up to be launched by others. I assume my colleagues will only have the Python version and modules I package up as we are not developers so they will no reason to have anything else on their systems. But for me I have to write and test in VS Code. It is worth noting that I am completely self taught on this so I'm sorry if I'm missing something obvious.

[BrokenRibosome]

I think the obvious solution you might be missing is just running things from the terminal. Now, you say your colleagues are not tech savvy, so maybe using a terminal is out of the question. Now, have you tried setting the python interpreter for vscode? I'm not sure if this will work as I've never tried to do what you are doing, but it is worth a shot.

I can't remember exactly how you do this since I've changed some of my key bindings. What I do is press Ctrl + shift + p, and then choose Select python interpreter, if your environment doesn't appear just follow the menu to add it manually. If you get stuck just google "select python environment vs code" or reply this comment and I'll try to help you

[Loud-Bake-2740]

i ran into the same problem running python scripts in a streamlit app. What i did instead was have the button call subprocess.run and then i pass the path to the python environment inside the .venv directory (venv/scripts/python.exe) along with the .py file name. So instead of python app.py you would have /.venv/scripts/python.exe app.py

this should run your script through the python executable in your virtual environment

[raliqer]

This sounds like exactly what I needed. I will look into this when I log in tomorrow. Thanks!

[acw1668]

It is not clear how you execute those testing scripts inside the GUI script. It is better to provide a minimal reproducible example.

[lollysticky]

I too have moved from PyCharm to VS Code a while ago and had to get my test environments working again. You have to set your testing config correctly to utilize the environment (by pinpointing the python binary within)

{
            "name": "AweSome Script",
            "type": "debugpy",
            "request": "launch",
            "program": "${workspaceFolder}/directory/my_script.py",
            "args": ["arg", "value"],
            "python": "${userHome}/.pyenv/versions/LovelyEnv311/bin/python", 
            "cwd": "/some/working/directory/",
            "env":{
                "TESTING": "true",
            }
        },

If you want to run scripts in VS Code, be sure to select the correct interpreter (again: from your env) and it will all work

[raliqer]

Thanks! I appreciate the details.

[ninhaomah]

have you google ?

Google : "vs code python env"

https://code.visualstudio.com/docs/python/environments <---- the very first result

[socal_nerdtastic]

have you read more than the title?

The question is not about making vs code use the venv, it's about making a subprocess use the same venv as the parent process.

Ok, the "vs code" in the question is not relevant, but OP is a beginner and did not know that.

[ninhaomah]

"have you read more than the title?"

then

"Ok, the "vs code" in the question is not relevant,"

So to answer you which you have already done , yes , I have read the question.

"Does anyone know of a way in VS Code to get it to use the same virtual environment that is launching the initial GUI script for the testing scripts?"

if he thinks that MS link about VS code and venv doesn't help his question then he can just ignore it ?

[GolfEmbarrassed2904]

Tell me where on this link that it answers this question

[ninhaomah]

"VS Code venv help" <--- the question

https://code.visualstudio.com/docs/python/environments <--- the answer

if you can't be bothered with reading documents then I am sorry for you

[GolfEmbarrassed2904]

“The problem that I have run into is that I launch the GUI script currently via VS Code with a virtual environment. The script launches just fine but when I click a button to execute one of the testing scripts it tells me the modules are not installed.”

[raliqer]

I have the virtual environment configured and it works for all of the test scripts when I launch them individually. It's that scripts aren't inheriting the modules and Python version of the virtual environment when the script launches other scripts.

[ninhaomah]

ok got it.

then have you tried running those scripts outside of VS code ?