-
Notifications
You must be signed in to change notification settings - Fork 110
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
Publish to PyPI #903
Comments
I'm not against the concept, the issue is that we have quite a few tools that need to be accessible after installation (combine.py, extract.py, analysis.py,...) and a lot of test scripts. Installing them into general PATH could easily be considered "polluting". while having simple How to make execution and discovery of those (you know, with tab-completion) easy is not something I have any experience with. Combine it with basically all of my focus for the past 4 years going towards Marvin Attack and yeah, such niceties are not stuff I end up working on. That being said, if you have an idea how to solve all of it in a general way (one that won't require any, or at most, very little changes to scripts) I'm fully open to discussing it, and once we agree on solution, reviewing the PR and getting it merged. |
So there are several ways this can be interfaced:
All of above can be implemented and combined, of course. And it wouldn't pollute As for the argparsing/CLI libs, the modern stdlib way is using argparse. And known third parties are Click and Typer. The Python 2.6 requirement has its limitations, though. |
ok, but this solves the issue of tools, it doesn't solve the issue for scripts. yes, py2.6 is a limitation, and I'd rather not introduce additional dependencies: as the project is now, it and all dependencies can be put in a single tarball that requires just the python executable to execute |
What do you mean? I thought I was talking about the scripts. |
What do you mean by that? Pure-python deps? |
by "scripts" I mean the files that live in by "tools" I mean the specific modules in the
for python-ecdsa and tlslite-ng (the only mandatory dependencies) to work, it's enough to do a symlink to the |
Hello, it doesn't seem like anybody brought this up in the future, but would you be open in publishing this to PyPI so that after a simple
pip install
, the scripts would be invokeable? I'll be happy to contribute packaging and GHA automations for this as well as looking into unifying the CLI required for this to function.This would allow people to use it, without having to jump through the hoops of executing several commands to set up the environment in an out-of-standard manner.
My motivation is that eventually it'd be nice to be able to integrate this into testing of web frameworks (I maintain CherryPy, Cheroot and aiohttp, for example).
The text was updated successfully, but these errors were encountered: