Konrad Hinsen skribis:
> On 15/01/2018 17:41, Konrad Hinsen wrote:
>
>> After a quick look at the definition of python-matplotlib, I suspect
>> that python-pyqt should be a propagated-input, not a plain input.
>> I will try this out as soon as possible.
>
> That was indeed the cause of the bug. I
On 15/01/2018 17:41, Konrad Hinsen wrote:
After a quick look at the definition of python-matplotlib, I suspect
that python-pyqt should be a propagated-input, not a plain input.
I will try this out as soon as possible.
That was indeed the cause of the bug. I have submitted a patch:
http://de
Fis Trivial writes:
>> Do you have a matplotlibrc file that sets a Qt-based backend? The default
>> backend is TkAgg, which does not require Qt. (Note that PySide is a Qt
>> interface for Python.)
>>
> I myself have never created such a file.
>
> I searched home with `find . -iname "*matplotli
>
> Do you have a matplotlibrc file that sets a Qt-based backend? The default
> backend is TkAgg, which does not require Qt. (Note that PySide is a Qt
> interface for Python.)
>
I myself have never created such a file.
I searched home with `find . -iname "*matplotlib*"`, didn't find the rc file
On 15/01/2018 14:04, Fis Trivial wrote:
* Steps to reproduce:
$ python
from matplotlib import pyplot
Do you have a matplotlibrc file that sets a Qt-based backend? The
default backend is TkAgg, which does not require Qt. (Note that PySide
is a Qt interface for Python.)
Konrad.
* Steps to reproduce:
$ python
>>> from matplotlib import pyplot
* Full message:
--8<---cut here---start->8---
Python 3.5.3 (default, Jan 1 1970, 00:00:01)
[GCC 5.4.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> from mat
