Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Design Issue: setup.py should be optional #31

Open
nil0x42 opened this issue Jan 7, 2019 · 0 comments
Open

Design Issue: setup.py should be optional #31

nil0x42 opened this issue Jan 7, 2019 · 0 comments

Comments

@nil0x42
Copy link
Contributor

nil0x42 commented Jan 7, 2019

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)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant