- a very basic docker-based quick start,
- a more advanced developer setup guide (using mixed docker/venv install),
- the original manual setup guide.
- Group Reviewers
- rDDOC9e6c2f3a614d: Split the getting-started guide in 3 parts
Also we'd like to install tox and pifpaf for running tests.
pip install $(./bin/pip-swh-packages --with-testing) tox pifpaf
Note: i needed to ask for wheel in the .venv, now i see it's already done by virtualenvwrapper! cool.
I'm a bit puzzled that with so many comments, this diff has been accepted! It should not have been so IMHO.
I initially only saw typos (and one missing flag).
It's not something that blocks a merge for me (even if i prefer we integrate without those ;).
As you did not merge it immediately though, i checked again but following the guide this time.
New remarks came.
I could have changed then but it did not occur to me.
Nope, WORKON_HOME is be the directory where virtualenvwrapper looks for known virtual envs.
Here we want to amend the postactivate script located in the bin directory of the current virtual env, thus in $VIRTUAL_ENV/bin (VIRTUAL_ENV is defined by venv, not venvwrapper).
To be really accurate, this should be
This is just the application of ckick's doc:
I do use the cdproject function to get back to this directory, so I do not really need such a variable. It could be added, but I won't add it now.
not at all