8 | | My problem has now gone away. I found a conda requirements file on our Github repo, removed my old unsuccessful environment and created the new environment, using "conda create" with the -f flag for the requirements file. This installs a conda version of pip, so that pip in that environment works consistently with conda. I think that conda cannot install the openslide binaries from C-code directly, and this has to be done by pip (but one must use the conda version of pip). Incidentally, although "import openslide" now works, the diff -r between the openslide packages on /opt/local and on ~/anaconda3, continues to give an identical answer to what I saw before, so my previous "test" using "diff -r" was misleading. I think all the binary files differ for both the failing environment and the new successful one. All the other files (python programs) are identical. |
| 8 | My problem has now gone away. I found a conda requirements file on our Github repo, removed my old unsuccessful environment and created the new environment, using "conda create" with the -f flag for the requirements file. This installs a conda version of pip, so that pip in that environment works consistently with conda. I think that conda on its own cannot install the openslide binaries from C-code directly, and this has to be done by pip (but one must use the conda version of pip). Incidentally, although "import openslide" now works, the diff -r between the openslide packages on /opt/local and on ~/anaconda3, continues to give an identical answer to what I saw before, so my previous "test" using "diff -r" was misleading. I think all the binary files differ for both the failing environment and the new successful one. All the other files (python programs) are identical. |