Comment Comment by cmcconomy My personal approach is:- use miniconda ONLY to create a folder structure to store packages and to specify a version of python (3.10 for example)- use jazzband/pip-tools' "pip-compile" to create a frozen/pinned manifest for all my dependencies- use pip install to actually install libraries (keeping things stock standard here)- wrap all the above in a Makefile so I am spared remembering all the esoteric commands I need to pull this all togetherin practice, this means once I have a project together I am:- activating a conda environment- occasionally using 'make update' from to invoke pip-compile (adding new libraries or upgrading), and- otherwise using 'make install' to install a known working dependency list. parent cmcconomy 3 years ago
- use miniconda ONLY to create a folder structure to store packages and to specify a version of python (3.10 for example)
- use jazzband/pip-tools' "pip-compile" to create a frozen/pinned manifest for all my dependencies
- use pip install to actually install libraries (keeping things stock standard here)
- wrap all the above in a Makefile so I am spared remembering all the esoteric commands I need to pull this all together
in practice, this means once I have a project together I am:
- activating a conda environment
- occasionally using 'make update' from to invoke pip-compile (adding new libraries or upgrading), and
- otherwise using 'make install' to install a known working dependency list.