On Tue, 20 Oct 2015, Daniel Stender wrote: > The problem here is #800788 (python3-astroid: not fit for Python 3.5), > which is upstream. > > If there isn't going to be fix in the short term a solution would be to build > requirements-detector temporarily against python3 instead of python3-all.
You later tagged this bug as wontfix. Can you explain the rationale? It doesn't make sense to keep a "wontfix" bug at severity serious... if you argue that the problem is in python3-astroid, then you should just reassign this bug and merge it with #800788. But right now python-requirements-detector will be removed in a few weeks due to this bug. And #800788 has not gotten the attention it deserves because it's only at severity normal while it arguably needs important or serious as the package will be broken as soon as Python 3.5 is the default. Ccing Sandro Tosi to bring his attention to #800788. Cheers, PS for Daniel: It's the third time in a month that I get a message that prospector will be removed due to some of its reverse dependencies and that's how I discovered this bug. :-) -- Raphaël Hertzog ◈ Debian Developer Support Debian LTS: http://www.freexian.com/services/debian-lts.html Learn to master Debian: http://debian-handbook.info/get/
