![]() Return _run_code(code, main_globals, None,įile "/Users/home/Dev/miniforge3/envs/napari-env/lib/python3.9/runpy.py", line 87, in _run_codeįile "/Users/home/Dev/miniforge3/envs/napari-env/lib/python3.9/site-packages/napari/_main_.py", line 424, in įile "/Users/home/Dev/miniforge3/envs/napari-env/lib/python3.9/site-packages/napari/_main_.py", line 420, in mainįile "/Users/home/Dev/miniforge3/envs/napari-env/lib/python3.9/site-packages/napari/_main_.py", line 230, in _run So I installed that as instructedĪlas, napari still won’t run: Traceback (most recent call last):įile "/Users/home/Dev/miniforge3/envs/napari-env/lib/python3.9/runpy.py", line 197, in _run_module_as_main Trying to run napari gave an error related to pythonw. This recognized all the manually installed requirements and was a success! Then, on a lark, I tried pip install napari Then I decided to try pip install "napari"īut this again devolved into trying ever lower versions of PyQt5. I then symlinked miniforge3/lib/python3.9/site-packagesĪgain, I verified that I can run a simple Hello World PyQt5 tutorial. The PyQt5 issue I attempted to resolve by installing PyQt5 using homebrew, since it didn’t seem to be on condo-forge as arm64. I did simple numpy, scipy, and scikit-image tests to ensure they were functional. I know numpy is supported on M1 as of 1.21, so I figured I’d install that, plus scipy and scikit-image using conda. Then when looking for PyQt5 it chain downgraded, so I killed it and started with a new conda napari-env. ![]() While attempting to install scipy it found incompatible numpy, so that failed. Then, I tried the base napari instructions, but with python 3.9 conda create -y -n napari-env python=3.9 I installed miniforge3 Conda, which is recommended by Apple and supports M1 native (arm64)
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |