Closed maresb closed 1 year ago
I updated the wiki installation instructions for now.
Excellent! That should solve this issue (I hope).
While we're thinking about it, it might be clever to add a "Fancy Install" section to Linux and Windows.
Suggestion for the Windows instructions:
...for those who would prefer to manage the GCC compiler installation on their own...
→
...for those who would prefer to manage the BLAS and GCC compiler installations on their own...
And then removing mention of Chocolatey (and also numba
?) we could copy "Fancy Install" to Linux/Mac.
We should probably mention in the case of M1 that we use OpenBLAS. (helpful link to the exact Conda package names)
Seeing this issue as well, downloading the beta release by default. And following the updated wiki instructions (>=4) I get the following error:
Encountered problems while solving:
- nothing provides vc 9.* needed by mkl-service-2.0.1-py27h0c8e037_0
ran it a second time and got something slightly different
Encountered problems while solving:
- nothing provides mkl >=2019.3,<2020.0a0 needed by mkl-service-2.0.1-py27h0c8e037_0
this was with mamba, not conda directly (Windows, AMD64)
interestingly this seems to be from using OpenBlas (nomkl)/mamba and using conda
directly and allowing mkl looks like it downloads correctly.
Closing because the installation instructions seem to have taken care of the primary issue. Also potentially surpassed by https://github.com/pymc-devs/pymc/issues/6750.
Description of your problem
Please provide a minimal, self-contained, and reproducible example.
On Linux,
results in the installation of
conda-forge/linux-64::pymc-4.0.0b6-py39ha563b64_0
. This beta version doesn't installmkl-service
and results inIt's reported that subsequent inference is very slow.
Please provide the full traceback.
Please provide any additional information below.
This was originally reported in https://github.com/conda-forge/pymc-feedstock/pull/41#issuecomment-1148135445 and https://github.com/conda-forge/pymc-feedstock/issues/43 but with slightly different conditions.
I have found two independent ways to resolve the issue:
conda install
command, indicate the version with"pymc>=4"
. A few caveats here: neitherpymc=4
norpymc=4.0.0
exclude4.0.0b6
. The quotation marks are mandatory to prevent Bash from interpreting the>
character as an output redirection to a file named=4
.I wrote some additional thoughts on this issue in https://github.com/conda-forge/pymc-feedstock/issues/43#issuecomment-1150957693.
I wonder if the installation instructions should be updated to recommend either or both of:
"pymc>=4"