On Thu, Feb 22, 2018 at 7:15 AM, Graham Wheeler <[email protected]> wrote:
> To be clear, when I said “virtualenv” I was talking about conda virtual > environments; I was not mixing them. > > Possibly what happened was a pip installed package pulled in some old > dependencies and things somehow got mixed up. I now suspect it was > nb-mermaid, as that was the only other thing I remember installing between > the time it worked and it broke. > This is my defense mechanism against that problem: https://github.com/fperez/copip it's hackish and I haven't taken the time to make it a clean, installable package, but it gets the basic job of 100% isolation between conda and pip done. Pip is an 'overlay' atop conda, which supersedes it in import priority but doesn't mingle in the filesystem, so any confusing side effects are easy to clean up if they ever arise. Cheers f -- You received this message because you are subscribed to the Google Groups "Project Jupyter" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jupyter/CAHAreOpN9CZuX0RUD%2B1-qzQEJDc3XJxKf1f_%2BCwUJPVJCKX1Gg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
