On Tue, 25 Aug 2015 19:32:16 +0200 Daniel Stender <deb...@danielstender.com>
wrote:
> On 25.08.2015 19:17, Gianfranco Costamagna wrote:
> ... yeah, this would be an option, Py3 as default is coming up, anyway.
>
> This is going to be an enhancement for Prospector, which is on Py2, but I
> think it runs Vulture
> as an app, an not imports anything from it.
>
> I'll take a look and come back!
I've rechecked now ... actually Prospector imports vulture.py to work with it.
A Py3 package
on the side would be reasonable to have it available when Prospector gets
transfered to Py3
some day in the future. There are also other reasons to prepare it, but to
build/run Vulture
solely on Py3 is a non option because of that.
A Py3 package on the side ... the binaries-have-conflict could be handled like
Jakub suggested
for python-afl.
For the name of binaries, I would prefer "vulture{,3}" over
"python{,3}-vulture" like Pylint does
it, but it appears Pybuild expects this ... does it?
Daniel
--
http://www.danielstender.com/blog/
4096R/DF5182C8
46CB 1CA8 9EA3 B743 7676 1DB9 15E0 9AF4 DF51 82C8
