-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Questions on virtual environment #7
Comments
Hi @dev-abir, The project directory doesn't have to be a Python virtualenv at all. It is not a convention to mix the virtualenv and the sources, it might even be a bad practice, but I put it like that in the README because it is convenient/easy to setup this way. I don't think it is worth mentioning in the README that the Python virtualenv can be elsewhere because I think that most experienced Python user will know how to customize their Python environment. What do you think ? Again, thank you for your feedback 🙏 |
I just needed to change just 2 lines to run The script assumes that the source directory is the virtualenv... And spits errors, if not so... You can just change |
I changed the path of the python3 binary according to your suggestion in commit 9161038. Can you test your setup with it and tell me if it is okay for you ? Thank you in advance 🙏 |
I have added some comments on your commit see this Not sure, if it's the right place... Maybe I should have told that here... |
Why the project directory needs to be a virtualenv? I have my virtualenv elsewhere.
I am not very experienced in python, is it a convention just to put virtualenv in the project directory, and gitignore/delete them manually later?(I don't think so...)
To get path of virtualenv, one can just use
VIRTUAL_ENV
environment variable, it is much robust(though I am not sure whether it works with all virtual environment packages or not). Moreover should we enforce everyone to use a virtualenv?The text was updated successfully, but these errors were encountered: