Arcane Hooker
I'm a hooker from Silvermoon City. Let me show you the Arcane way to Python
Hooker is a hooking library that tries to simplify event firing and catching. It gives the ability to plugin creators to create plugins for many different parts, without having to break the logic in separate destinations, if it's not needed. The main features include:
- Event declaration with help message support
Waterfallevents that pass their output as arguments to next hook- Simple CLI tool to view all defined events of a project and its help messages
- Functions decorators to hook on events
- Dependency requirement for hooks (
ahook has to be run beforeb) HOOKER_SCRIPTSenvironmental variable allows to load additional scripts (aka plugins)- Wildcard hooks that are fired on all events
- When a hook accepts the
__retvals__argument, the returned values of the previous hooks (and the whole hook functions) will be passed into it as an OrderedDict - Python 2 compatibility - I'll try to keep that for as long as I can
Terminology:
Project: A project that uses HookerPlugin: A piece of code that adds functionality to aProjectusinghooksEvent: A name for something thatPluginscan hook on. It is called on specific times (that theProjectauthor has programmed) so thatPluginscan add functionalityHook: A function that thePlugincreator wrote and is declared as hook using the@hooker.hookdecorator. Contains at least oneEventname (or none if its a wildcard hook) and optionallyDependenciesDependency: AHookcan declare to be called after a plugin has run.Dependencycan include the name(s) of the python module(s) (NOT the function name) that include hooks that need to be run before theHook
For documentation check the wiki
Installation
pip install -U hooker
Usage
To find defined hooks in a project use python -m hooker <python file/module directory>
Example:
$ py -m hooker example/crypter/crypter.py
pre_open_in: Input file will open. Arguments: path<str>. Return: path<str> - /home/dzervas/Lab/satori/hooker/example/crypter/crypter.py:6
pre_open_out: Output file will open. Arguments: path<str>. Return: path<str> - /home/dzervas/Lab/satori/hooker/example/crypter/crypter.py:7
encrypt: Encrypt data. Arguments: data<bytearray>. Return: data<str> - /home/dzervas/Lab/satori/hooker/example/crypter/crypter.py:8
decrypt: Decrypt data. Arguments: data<bytearray>. Return: data<str> - /home/dzervas/Lab/satori/hooker/example/crypter/crypter.py:9
As a Project Author to use hooker you have to declare an event and then fire it
Example:
# project.py
import hooker
hooker.EVENTS.append("test", "Fired after Hello World is printed")
print("Hello World")
hooker.EVENTS["test"]()
As a Plugin Creator to extend a project using hooker, you have to create a function
using the @hooker.hook decorator and define the event you want to hook on:
Example:
# my_plugin.py
import hooker
@hooker.hook("test")
def hello():
print("Goodbye World")
Now to use the plugin, you either have to import it in the project, or execute the
project using the environment variable HOOKER_SCRIPTS as follows:
$ HOOKER_SCRIPTS=my_plugin python project.py
Hello World
Goodbye World
Used in
While the code is not a mess, I'm using a fair bit of python magic. The target is to provide the simplest and most convenient API for both project and plugin authors.
If you have a better way to do something, at least open an issue to discuss it, I'm very interested!
Happy Hacking! :)
Metadata
Release files for hooker 1.0.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| hooker-1.0.2.tar.gz | 27.9 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| hooker-1.0.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 43.8 kB
Release files / hooker-1.0.2.tar.gz
| Download URL | hooker-1.0.2.tar.gz |
|---|---|
| Size | 27.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
dcc72c8045ac3449e1661d70514219e96193182316d42cd9738118be3880010b
|
|
BLAKE2b-256 checksum How to use checksums |
88084f230331da52f7c1c06778fadaa1be33ac224ef669163f77ff7700ba3377
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.10.9
|
Release files / hooker-1.0.2-py3-none-any.whl
| Download URL | hooker-1.0.2-py3-none-any.whl |
|---|---|
| Size | 15.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
19f9ca06f2e1bddb6a0c475d6f4bd5f1f9d66eca68bf1c53a8cf0a3793c5521e
|
|
BLAKE2b-256 checksum How to use checksums |
151d12d351e52ac8b896338ca79d69153e38b90813faeadca37038b4a818af7f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.10.9
|
Security for hooker 1.0.2
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.