Closed twiecki closed 1 year ago
Can you try again? Maybe the package was not available yet when you tried. I don't have a mac but I tried a dry-run in a mock env and I could see it there:
CONDA_SUBDIR=osx-64 conda create --name TEST "pymc=5.2.0" --channel conda-forge --dry-run
Still doesn't work.
On Tue, Apr 11, 2023 at 1:58 PM Filipe @.***> wrote:
Can you try again? Maybe the package was not available yet when you tried. I don't have a mac but I tried a dry-run in a mock env and I could see it there:
CONDA_SUBDIR=osx-64 conda create --name TEST "pymc=5.2.0" --dry-run
— Reply to this email directly, view it on GitHub https://github.com/conda-forge/pymc-feedstock/issues/77#issuecomment-1503194628, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAFETGCRUKQSTXBZUBZQTS3XAVBM3ANCNFSM6AAAAAAWZNPGEM . You are receiving this because you authored the thread.Message ID: @.***>
pymc-base
Are you trying a fresh env as in my example above? What is the output of,
conda create --name TEST "pymc=5.2.0" --channel conda-forge
?
Huh, that seems to work. Weird. Is my env borked?
On Tue, Apr 11, 2023 at 2:09 PM Filipe @.***> wrote:
pymc-base
Are you trying a fresh env as in my example above? What is the output of,
conda create --name TEST "pymc=5.2.0" --channel conda-forge
?
— Reply to this email directly, view it on GitHub https://github.com/conda-forge/pymc-feedstock/issues/77#issuecomment-1503214348, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAFETGF2VQXV76ZG7PXJVVDXAVCWJANCNFSM6AAAAAAWZNPGEM . You are receiving this because you authored the thread.Message ID: @.***>
Huh, that seems to work. Weird. Is my env borked?
You probably have packages that are not compatible with the pymc 5.2.0 dependencies. If you have mamba
you can try this on your .condarc
to see better error messages on the conflicts:
experimental_sat_error_message: true
doesn't display anything, but closing since it's not a problem with thep ackage.
Comment:
On OSX:
mamba install pymc==5.2.0