I’ve had a lot of problems lately with installing pymc3 for both dev and use. I tend to use environments for development work but keep a “base” for production, but I’ve had so many problems keeping pymc3, pymc-theano, aesera and arviz up to date in this env - there seem to be a lot of clashes resulting in failed solves and a corrupted environment. Indeed, even with a brand new env, following the pymc3 install instructions still results in a failed solve.
As an example, attached is the output from a new python 3.9 environment, having installed pymc3 per instructions, and then just adding the rather vanilla spyder kernel so that I can use spyder in this env.
If this situation is not unique to my setup, can I suggest getting a (more or less) frozen final pymc3 release on conda that doesn’t corrupt environments?
Sorry to be identifying a problem without being able to offer a solution, but I’m not dev-enough to help with getting a stable conda version setup.
here_be_dragons.txt (145.0 KB)