mnelab: Installation problems on Windows

Using the default command pip install mnelab on Windows I get:

Installing collected packages: PyQt5, mnelab
Could not install packages due to an EnvironmentError: [WinError 5] Access is denied: 'C:\\Users\\mmagn\\Continuum\\anaconda3\\Lib\\site-packages\\PyQt5\\Qt.pyd'
Consider using the `--user` option or check the permissions.

strangely, I get it even when I run it in command prompt with administrator privileges. When I run using pip install mnelab --user the script the mnelab.exe is put in a separate directory and does not do anything. When I then first activate my base anaconda env (it is my default python so I don’t know why it makes any difference) and then do pip install mnelab - I get everything installed in one directory but mnelab.exe still does not work. When I try to import mnelab in python I get:

Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "C:\Users\mmagn\Continuum\anaconda3\lib\site-packages\mnelab\__init__.py", line 1, in <module>
    from .mainwindow import MainWindow
  File "C:\Users\mmagn\Continuum\anaconda3\lib\site-packages\mnelab\mainwindow.py", line 7, in <module>
    from PyQt5.QtCore import (pyqtSlot, QStringListModel, QModelIndex, QSettings,
ModuleNotFoundError: No module named 'PyQt5.sip'

I might have been unlucky - I can test tomorrow on other Windows computers.

About this issue

Original URL
State: closed
Created 5 years ago
Comments: 27 (19 by maintainers)

Commits related to this issue

DOC: Urge users to install into dedicated conda env x-ref GH-33 — committed to hoechenberger/mnelab by hoechenberger 5 years ago
DOC: Urge users to install into dedicated conda env (#35) * DOC: Urge users to install into dedicated conda env x-ref GH-33 * DOC: Style; add entry point command for pip instructions * DOC:... — committed to cbrnr/mnelab by hoechenberger 5 years ago

Most upvoted comments

Often one might want to use defaults channel as the default and only install packages not present there from conda-forge, especially in the base environment, like:

conda install -c defaults -c conda-forge mnelab

Anyway python packaging is notably horrible, and almost always good idea to use environments.

teekuningas on Jul 3, 2019

Yes, let’s wait. Just to make it clear, pip install --no-deps mnelab would have worked in his case.

cbrnr on Jul 4, 2019

Yes, I don’t need mayavi 😄 - but I get the point, my setup is very special, so let’s not get into that. If someone really wants to install a barebones MNE + MNELAB in a conda base env, they will figure it out (or I will tell them upon request).

cbrnr on Jul 4, 2019

You’re the conda expert, so if you say it should be done as it is currently in the README, there’s no need to describe a stupid way. Also, let’s make things not overly complicated - if someone uses conda there is one way to install it.

cbrnr on Jul 4, 2019

😄 I have very similar experience but with pip - but its most likely because I’m a windows user, and pip can sometimes be horrible on windows.

Yep, I can only speak for macOS/Linux.

Anyway - using a separate env works well, so I still think it might be good to recommend setting up a separate env for mnelab more strongly in the docs.

The code explicitly creates a new env, but if you want we can also re-word the preceding sentence. However, I’d be interested if this is specific for this package - but this should be discussed at https://github.com/conda-forge/mnelab-feedstock/issues.

cbrnr on Jul 3, 2019