Open ned2 opened 6 years ago
Seems pragmatic to me. I'm planning to spend all of the Saturday session doing my own exploration, but hopefully by the end of that sesh we'll have some more concrete ideas and can start planning out pathways for joint tasks, which will benefit from the shared virtualenv.
I propose that we adopt a shared Python environment. This would not be required for exploratory work, but as we move towards development of a codebase for the data2app porject, this will become important.
The toolchain @norrishd and I use for Python is based on pyenv and pip-tools. Together this is comparable to what pipenv gives you. pipenv is probably great, but I have a fair bit of experience using this tool chain for managing Python projects so would be able to create some resources for getting everyone started.
How do people feel about adopting something along these lines?
https://github.com/pyenv/pyenv https://github.com/jazzband/pip-tools
Also, to clarify, I don't mean a single virtualenv. This would allow us to maintain multiple sets of dependencies for different virtualenvs. I currently have an example in venvs/shared. We could also have eg
venv/insights
venv/data2app
venv/dask-fun
etc