Bug#757645: Rationale for the change

Gianfranco Costamagna costamagnagianfranco at yahoo.it
Mon Aug 18 06:22:11 UTC 2014


Hi Frédéric and Yuri,

First of all, thanks to you both for the bug report.

In only one month is good to see people complaining and to see the increased popcon :), so thanks for using the package and for the bug report.

I'll try to explain with a simple example the reason for this change:
python /usr/lib/python2.7/dist-packages/pyqtgraph/examples/__main__.py

the example code shows you the CLIExample window, when you can write and run easily the code, with the useful list of the examples on the left, where you can choose to force PyQt, or PySide as rendering engines.

Since also my first sponsor got some troubles in running them (if you choose pyside without having it installed you will likely have a import error and in some cases a segfault, IIRC), and since I'm a person that _really_ likes to install and run things, rather than install, run/fail/run/fail/check_faults/change_library, I choose to go for having them both required.

Unfortunately I understand this change is good for people approaching for the first time to the package, while for code already in place is really an overread.

For this reason, since I really want to fix this issue, I ask to you both how to proceed.
What comes in my mind is:
A) provide a python-pyqtgraph-examples with them both, and leave python-pyqtgraph have the choosable dependency qt|side (and maybe a recommend or suggest for the examples package), this will go in new, and I can catch the ball for adding a -doc package (upstream asked me to add it, I just need to tweak a little bit the package, the change should be trivial).

B) revert this change, having a possible not fully working example suite (bad idea for people like me, but I'm just a clueless maintainer with no strong opinion on this)


C) something that I didn't think about, but maybe possible (usually a DD comes here with a great and simple solution I didn't think about)



In my opinion A is the best solution (didn't come in my mind when I firstly thought about this problem), but I really would like to hear some feedbacks ;)


BTW I'm a quite old DM, but I'm not in the dm.txt list for this package, so would be nice to have a sponsor for the change ;).

Gianfranco



More information about the debian-science-maintainers mailing list