Clone repo first, then create .venv folder within the repo. Current instructions said to clone the repo into the venv folder, which is generally not a good idea. Use .venv name which VSCode and PyCharm tend to recognize better.
Rearranges the first time contribution section to explain a bit more about git, GitHub, and the virtualenv, and the proper order that parts happen in.
fixes #671
alternative to #698
(I started working on this at the PyCascades sprint before I noticed either of these.)
Clone repo first, then create
.venvfolder within the repo. Current instructions said to clone the repo into the venv folder, which is generally not a good idea. Use.venvname which VSCode and PyCharm tend to recognize better.Rearranges the first time contribution section to explain a bit more about git, GitHub, and the virtualenv, and the proper order that parts happen in.
fixes #671 alternative to #698 (I started working on this at the PyCascades sprint before I noticed either of these.)