You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I found that installation on MacOS was far from straightforward and it took me more than an hour of troubleshooting to get it working. Documenting all of the extra steps required will help people in future.
The conda-forge channel was required in order to create the virtual environment: conda config --append channels conda-forge
QT5 needs to be installed system wide:brew install qt5
qmake executable needs to be available on the system path: brew link qt5 --force
Installing PtQt5 from requirements.txt does not work because it hangs on a license acceptance step. This can be circumvented with pip install PyQt5==5.15.9 --force-reinstall --config-settings --confirm-license= --verbose
Then the rest of the dependencies can finally be installed: pip install -v -r "requirements.txt"
The text was updated successfully, but these errors were encountered:
Thank you for your collaboration! I’m currently a bit busy, but if you’d like to create a Pull Request updating the MD file that describes the installation process to include all the necessary steps for a correct installation on macOS, I’d be more than happy to review and approve it.
I found that installation on MacOS was far from straightforward and it took me more than an hour of troubleshooting to get it working. Documenting all of the extra steps required will help people in future.
conda-forge
channel was required in order to create the virtual environment:conda config --append channels conda-forge
brew install qt5
qmake
executable needs to be available on the system path:brew link qt5 --force
requirements.txt
does not work because it hangs on a license acceptance step. This can be circumvented withpip install PyQt5==5.15.9 --force-reinstall --config-settings --confirm-license= --verbose
pip install -v -r "requirements.txt"
The text was updated successfully, but these errors were encountered: