python-venv

问题 As of python 3.3 the stdlib has the venv module for creating virtual environments. Are python 3.x venv environments relocatable? 回答1: Nope, commands installed in ./bin have fixed paths in shabang lines. 来源： https://stackoverflow.com/questions/27186207/are-python-3-x-venv-environments-relocatable

问题 As of python 3.3 the stdlib has the venv module for creating virtual environments. Are python 3.x venv environments relocatable? 回答1: Nope, commands installed in ./bin have fixed paths in shabang lines. 来源： https://stackoverflow.com/questions/27186207/are-python-3-x-venv-environments-relocatable

问题 I am following a tutorial on virtual environments (for Python) from the Coding Train (Here: https://www.youtube.com/watch?v=nnhjvHYRsmM). As I follow the tutorial, I see that, when which python is typed (in Terminal), the output should be the venv's Python in which it had installed. However, my system, for whatever reason this may be, decided to use it's own installed version of Python, instead. This means that all the dependencies (/modules) are screwed up and that I can't simply type out

问题 I'm using a django_crontab library and it worked fine until I decided to export my SECRET_KEY to an environmental variable. Summing up what I have done in bash (while in my venv): export SECRET_KEY='some_secret_key_from_settings' In settings.py: SECRET_KEY = os.environ['SECRET_KEY'] In addition, I use venv, so I've also added this to settings: CRONTAB_PYTHON_EXECUTABLE = '/path_to_my_venv/venv/bin/python3' This is the error that I have: SECRET_KEY = os.environ['SECRET_KEY'] File "/Library

问题 I'm using a django_crontab library and it worked fine until I decided to export my SECRET_KEY to an environmental variable. Summing up what I have done in bash (while in my venv): export SECRET_KEY='some_secret_key_from_settings' In settings.py: SECRET_KEY = os.environ['SECRET_KEY'] In addition, I use venv, so I've also added this to settings: CRONTAB_PYTHON_EXECUTABLE = '/path_to_my_venv/venv/bin/python3' This is the error that I have: SECRET_KEY = os.environ['SECRET_KEY'] File "/Library

问题 An initial pyvenv3.5 venv at create time is about 9.5MB on disk, before adding any custom content. Over 9% (!) of the venv disk-overhead are *.exe files, but all lack execute permission mode. One example: lib/python3.5/site-packages/setuptools/gui-32.exe . The linux file command says they are: executable for MS Windows . It looks like an obscure OS I'm certain my many pyvenv will never run on, and on which I'm unable to test. What are the repercussions if I just delete them? In initial tests

问题 i'm working on python 3.7 with Linux Ubuntu 18.04 and i'm trying to import a requests from the venv that i've created. What I have done is install python3.7 and set it to the default via vim ~/.bashrc . When I type python -V in the terminal, it now prints python 3.7.3 . I've also installed VirtualEnv with this tutorial and installed the venv to my project directory. Within the project directory, I can clearly see that the venv as well as the other folders such as bin , include , lib , share

问题 i'm working on python 3.7 with Linux Ubuntu 18.04 and i'm trying to import a requests from the venv that i've created. What I have done is install python3.7 and set it to the default via vim ~/.bashrc . When I type python -V in the terminal, it now prints python 3.7.3 . I've also installed VirtualEnv with this tutorial and installed the venv to my project directory. Within the project directory, I can clearly see that the venv as well as the other folders such as bin , include , lib , share

问题 How can I downgrade the Python version from 3.8 to 3.7 in my virtual env? I have to install tensorflow 1.14, therefore I'm trying to downgrade the Python version. Is there a command for it using pip? 回答1: You can install multiple Python versions and set separate environment variables for each version. If you use Anaconda you can also create separate virtual environments with different python versions: conda create --name myenv --python=3.7 Or you can use something like pyenv-win to manage

问题 In my project I use the built-in python virtual env ( python -m venv ). To set environment variables I add multiple export VAR1=VALUE1 to the end of the venv/bin/activate . Obviously, when I delete the venv and create a new one, for example with the new python version all my env variables get lost. So, is there a way to preserve them? May be it is possible to define env variables when creating the venv? 回答1: instead of adding to activate export VAR1=VALUE1 consider writing them into their own