On 10.11.2015 09:10, Raphael Hertzog wrote: > 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. :-)
Hi Raphaël, I was about to contact you, this issue gets pressing now. That's a good suggestion how to treat this bug report better. Thanks! Working on merging the bugs ... Best, Daniel -- 4096R/DF5182C8 46CB 1CA8 9EA3 B743 7676 1DB9 15E0 9AF4 DF51 82C8 LPI certified Linux admin (LPI000329859 64mz6f7kt4) http://www.danielstender.com/blog/
