Skip to content
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

Use a python virtual environment for every module #27

Closed
davideaimar opened this issue Oct 30, 2021 · 0 comments · Fixed by #29
Closed

Use a python virtual environment for every module #27

davideaimar opened this issue Oct 30, 2021 · 0 comments · Fixed by #29

Comments

@davideaimar
Copy link
Member

We can multiple python virtual environments for managing dependencies of every module.

Ideas:

  • create a venv folder not committed inside every module python3 -m venv /path/to/new/venv.
  • create a requirements.txt file inside every module that contains all the versioned dependencies of that module (can be done using `pip freeze > requirements.txt)
  • activate the venv using source venv/bin/activate, check if you are in the venv just by looking at the benginning of the line, you should have (venv) written. (we also have to use this environment in the services)
  • install the dependencies using pip install requirements.txt (they will be installed only for that specific environment)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants