Re: reducing matplotlib2 build-depends.

2019-11-13 Thread Dmitry Shachnev
Hi Sandro! On Tue, Nov 12, 2019 at 09:10:49PM -0500, Sandro Tosi wrote: > well, i dont think it's a good reason to just stop testing complex > software tho. some of those dependencies are required so that mpl can > build extensions (in particular for the GUI backends) so if you remove > them, the

Re: reducing matplotlib2 build-depends.

2019-11-12 Thread Sandro Tosi
On Tue, Nov 12, 2019 at 9:24 AM peter green wrote: > I am guessing that many of these are to get testsuite coverage for optional > features and are not strictly needed for the build, while testing stuff is > nice I don't think it's vital for software that is on it's way out. I tried > removing

Re: reducing matplotlib2 build-depends.

2019-11-12 Thread Rebecca N. Palmer
By itself, removing those dependencies reduces the big tangle [0] from 148 packages to 141, the freed ones being: ipywidgets pyqt5 pep8 autopep8 xcffib xlwt cairocffi. (Note that "not in a tangle" means "no *circular* dependencies", *not* "leaf / can be removed immediately".) There may also

Re: reducing matplotlib2 build-depends.

2019-11-12 Thread Dmitry Shachnev
Hi all, On Tue, Nov 12, 2019 at 02:13:51PM +, peter green wrote: > matplotlib2 seems to be an important node in the python2 removal/reduction > problem (and the qt4 removal problem). I have noticed there are a > substantial number of python module packages that it build-depends on but > does

reducing matplotlib2 build-depends.

2019-11-12 Thread peter green
matplotlib2 seems to be an important node in the python2 removal/reduction problem (and the qt4 removal problem). I have noticed there are a substantial number of python module packages that it build-depends on but does not depend on. python-backports.functools-lru-cache python-cairocffi