-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
installing pwntools pollutes /usr/local/bin #2361
Comments
Do you suggest something or just document the current behaviour? Do you want to toggle the default and not create scripts by default? Or only for a few commands? I agree "update" and "template" are very generic indeed. We can filter some weird ones out? |
I do not have a preference about the default behavior (the flag), but, the bash/zsh completion currently only works under Finally, we should update the doc https://github.com/Gallopsled/pwntools/blob/dev/docs/source/install.rst#command-line-tools |
And it seems installing pwntools through homebrew do not have chance to set |
Would you mind proposing a pull request please? I don't own a Mac so can't tell for the homebrew install too. |
According to #660, the original plan was to use a single entry point, which is in my favour. Removing scripts in setup.py will take effect at next upgradation. So we need deprecation before actually removing them, in case there are shortcut users. The two steps:
|
@tkmikan does this command work for you? I still get all of the CLI binaries installed. According to this [1], maybe it actually shouldn't work with install? Hoping to get rid of these annoying CLI binaries except |
Just run into this. After getting rid of 3.11, for some reason packages remained and now unable to get rid of those scripts automatically. I would appreciate some cleanup script for botched uninstallation. :/ Other than that thanks for the great job and maintenance of this package :) |
For a long time, installing pwntools will create console scripts for all files under
pwnlib/commandline
to/usr/local/bin
(or other equivalent path).(Dry-)Running
pip uninstall pwntools
will show the files it creates, includingAs command accessible globally in PATH,
checksec
hex
)debug
template
update
version
)main
andcommon
is not a command at all.These commands can actually be invoked
pwn subcommand
.And, the usage help always prepend
pwn
before the actual script name.Although there is a flag
--only-use-pwn-command
, I believe few people know it and use it.The text was updated successfully, but these errors were encountered: