Bug#826042: Spyder crashes on start

[Ghislain Vaillant]

On 24/07/16 21:10, Jitse Niesen wrote:
> On 18/07/16 15:15, Ghislain Vaillant wrote:
>>
>> If you want to be helpful, please consider reviewing whether the
>> current state of Debian unstable and check whether it contains all the
>> necessary dependencies for the packaging of Spyder 3.x to happen.
>
> It's possible to run Spyder, but I don't think everything is ready for
> it yet. Specifically, I can install (with "python setup.py install") and
> run Spyder after I installed the following packages from Debian unstable:
>
> python3             3.5.1-4
> python3-docutils    0.12+dfsg-1
> python3-jinja2      2.8-1
> python3-pickleshare 0.7.3-1
> python3-qt4         4.11.4+dfsg-2
> python3-qtawesome   0.3.3-3
> python3-qtpy        1.1.1-1
> python3-sphinx      1.4.5-1
> python3-zmq         15.2.0-1
>
> However, Spyder complains of missing dependencies and while the basic
> functionality is there, not all features work correctly. Some of them
> can be installed from unstable:
>
> python3-jedi        0.9.0-1
> python3-pep8        1.7.0-2
> python3-psutil      4.2.0-1
> python3-pyflakes    1.2.3-1

Thanks Jitse for this listing. This is very helpful.

> Spyder has three further dependencies that need more work:
>
> * rope >= 0.9.4: There is a package python-rope version 0.10.2-1 but
>   no Python3 version.
>
> * qtconsole >= 4.2.0: Experimental has jupyter-qtconsole.
>
> * nbconvert >= 4.0: As far as I can see, there is no nbconvert but
>   there is an Intend-To-Package message at bug 801058.

As you can see here:

   https://lists.debian.org/debian-python/2015/09/msg00087.html

nbconvert is further along in the dependency chain, hence yourself not
finding an RFS for it yet. I believe Julien is working on it. Meanwhile
other dependencies like ipython and the jupyter core packages will have
to find their way to the archive (first via a trip to experimental)
first, before nbconvert is made available.

Regarding rope, the package has a wishlist bug for Python 3 and also a
CVE (which is bad). It might be worth checking with the package 
maintainer whether he still actively maintains it, and propose a
migration to the DPMT Git. I'll contact him and propose my help.

Cheers,
Ghis