The Qt binding mess about neurocurator HOT 5 CLOSED

The following package could be very useful in abstracting this problem: https://pypi.python.org/pypi/QtPy . This is used by the Spyder project (https://github.com/spyder-ide/spyder). Inspiration can be taken from this project on how to manage Qt bindings properly.

from neurocurator.

Other potential avenues to consider (listed for brainstorming only):

• Docker install
• Freeze as an executable
• Move from Qt to a web-based interface (on longer term because this is likely to require a significant amount of work and time)
• (to be completed)

from neurocurator.

Some notes as of 01.02.18:

• Docker isn't for GUI applications like NeuroCurator,
• freezing as an executable has been done between October 2017 and January 2018 but has a high cost on the releasing process and isn't Python style,
• a web-based interface isn't currently the goal,
• QtPy, from the Spyder project, might be in danger as the Spyder project is unfunded since November 2017,
• PySide2 is still not considered stable,
• migrating to Qt 5 is blocked by the need to stabilize the current code base.

As of v0.4.1, the new installation procedure mitigates this issue using conda-forge for PySide and Qt.
https://github.com/BlueBrain/neurocurator/blob/v0.4.1/README.md#getting-started

from neurocurator.

We will want to check Qt.py as an alternative to QtPy.
See also: https://github.com/mottosso/Qt.py#projects-similar-to-qtpy.

from neurocurator.

Fixed in NeuroCurator v0.4.4 by porting to Qt 5.11 and PyQt 5.11.

PyQt5 has been chosen instead of Qt for Python (PySide2) because there is no Poppler binding for PySide2. As currently it does not make sense to also be compatible with PySide2, no abstraction layer (Qt.py, QtPy, ...) has been used.

from neurocurator.