MetaCell / nwb-explorer

NWB Explorer is a web application to visualise and analyse the content of NWB:N 2 files
Other
22 stars 16 forks source link

error installing nwb explorer using python 3.10 #302

Open anhknguyen96 opened 2 years ago

anhknguyen96 commented 2 years ago

Hi, I installed nwb explorer using python 3.10 and ran into this error (photos attached), but the installation worked in python 3.9 and 3.8. Compatibility issue?

python3-10-install-err python3-10-install-err1

sanjayankur31 commented 2 years ago

I think NWBE is currently limited to py3.7: https://github.com/MetaCell/nwb-explorer/blob/master/setup.py#L40

If it worked with 3.9, but not with 3.10, then we need to look into what's changed between the two versions and double-check if all our dependencies are py3.10 ready. This particular error is coming from pyecore, so the first step would be to check if that is py3.10 ready or not.

PS: would it be possible to paste errors as text please? Images can't be searched for text, and they're not accessible to visually impaired users that rely on screen readers and so on either.

sanjayankur31 commented 2 years ago

pyecore is still limited to py3.9, so we can't quite use 3.10 yet even if we update to the latest version of pyecore:

https://github.com/pyecore/pyecore/blob/master/setup.py#L49

filippomc commented 2 years ago

While this gets fixed, I suggest to use a conda (or equivalent) virtual environment to control the Python version as indicated in the main README

sanjayankur31 commented 1 year ago

Note: pyecore now supports python 3.10+. Tested with a new virtual environment here with python 3.11.3, and it installed fine using pip.

susiefeng commented 10 months ago

Hi! I have python3.7.16 in my env but I ran into the install error when running python utilities/install.py

below are error message: note: This error originates from a subprocess, and is likely not a problem with pip. error: legacy-install-failure

× Encountered error while trying to install package. ╰─> nwb-explorer

note: This is an issue with the package mentioned above, not pip. hint: See above for output from the failure.

Any advice? Thanks!

filippomc commented 10 months ago

Hi @susiefeng, the information provided is not sufficient to debug the issue, looks like it's related to the Python env. I strongly recommend to use a virtual environment (I use miniconda), to start from a fresh python environment as indicated in the instructions in the README.