doc: use virtual env for installation #167
Conversation
| Next, create a `virtual environment <https://docs.python.org/3/library/venv.html>`__:: | ||
|
|
||
| $ sudo -H pip install -e . | ||
| $ python3 -m venv ~/luma-env |
There was a problem hiding this comment.
I tend to use:
python3 -m venv .venv
.venv/bin/activate
I think IDEs like vscode and tools like pyenv will sniff out a .venv directory and will auto-activate it.
Is there any reason not to stick to that convention?
There was a problem hiding this comment.
Or are you aiming to pull all the dependencies for all sub-projects into one place?
There was a problem hiding this comment.
Is there any reason not to stick to that convention?
I didn't know that IDEs like vscode and tools like pyenv will sniff out a .venv directory and will auto-activate it, but maybe I'm just old-skool :-/
There was a problem hiding this comment.
Is there any reason not to stick to that convention?
I like to know where my virtual envs live, explicitly, in this case ~/luma-env, and since I didn't know about that convention (and new users wont either i'd guess) I chose this.
|
Is there an update to this PR? There is a docu enhancement I'd like to add after the PR has been merged. @thijstriemstra 's change would be consistent with the installation instructions in other luma docs like https://luma-oled.readthedocs.io/en/latest/software.html |
|
fixes #166