In python & other interpreted language projects, it is a good practice to provide a setup routine, as an equivalent of the traditional make install.
Therefore, the installation (here, setup.py) should always be optional, and the user should be able to run the project as soon as it was cloned.
Most people like to test a tool before actually installing or packaging it into their system (this assertion is even more true for pentesters, who clone & test tools thousands of times per year)
In python & other interpreted language projects, it is a good practice to provide a
setuproutine, as an equivalent of the traditionalmake install.Therefore, the installation (here,
setup.py) should always be optional, and the user should be able to run the project as soon as it was cloned.Most people like to test a tool before actually installing or packaging it into their system (this assertion is even more true for pentesters, who clone & test tools thousands of times per year)