Update project setup documentation to clarify virtualenvwrapper init (fix #70)

[x0s]

This PR aims at updating the documentation to clarify environment setup and avoid python 2/3 conflict. Therefore it resolves #70

[x0s]

Hi @frgfm , any idea why the checks are failing and still using circle ci ?

[frgfm]

Regarding CircleCI, as some PRs were still pending when CI was changed, I left the webhook while they are not merged. For the checks, it's strange, I'll try something in another PR to address this while adapting your suggestions from #68!

[frgfm]

Same thing here, I think you just need to make any commit to trigger the workflows :)

[x0s]

@frgfm: Could you see any way the tests can fail with such changes in the code base so you are asking again to write fake commits ?

Those for migrated in a hurry from circleci to workflows may take their responsability in this regard. IMO, asking others to fiddle with their PRs is not a good way to maintain the repository.

[frgfm]

@frgfm: Could you see any way the tests can fail with such changes in the code base so you are asking again to write fake commits ?

Those for migrated in a hurry from circleci to workflows may take their responsability in this regard. IMO, asking others to fiddle with their PRs is not a good way to maintain the repository.

Not at all, I'm happy reviewing this. You specifically asked me why the CI would fail, I'm suggesting a way to handle this. But with this change, I agree that untriggered tests are not a big issue.

[frgfm]

Thanks for the PR!