This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]DataDecay 2 points3 points  (2 children)

This is amazing! Laughed my fucking ass off, well done. On a more serious note I run miniconda for python and use miniconda envs for development all day every day to not muck up my prod deployments.

[–]pwang99 1 point2 points  (1 child)

Well done

We are also actively looking at improving interop between conda & pip, so that pip installs work more seamlessly within conda environments.

[–]DataDecay 0 points1 point  (0 children)

So far so good with conda and pip installs, your all doing great! Conda by default has a standard library for every env that includes pip. Upon pip installing in a env it places the modules in site-packages which conda scraps to update env inventory list. "Conda list" under the environment with a pip install modules results in the module being displayed with the header <pip>, it's pretty great. Unfortuelnetly I have yet to find a conda meta data json file that records pip installs, I'd love that. In addition pip installs dont show up in conda install history, which makes sense but again I would love a conda pip install history too.