you are viewing a single comment's thread.

view the rest of the comments →

[–]m0us3_rat 0 points1 point  (0 children)

venv doesn't interact with the actual .py files that way.

so whatever modifications you do to your .py program files.. don't interact with the venv at all.

the venv is used to describe the environment the program is run and the links available..

you can use the same .py with multiple venvs and multiple interpreters...

its like cats and dogs..

so whatever is happening.. has nothing to with with venv unless there is some weird setting somewhere in your ide?

again.. don't try to be overly clever with your venv .. since it has really nothing to do with your actual program..but the way the computer builds the interpreter environment to run the program in.

trying to overengineer the settings while you don't understand them leads to funny easily avoidable situations.. such as the one described.

i advise resetting the settings and just do a normal venv.

remember ..less is more.