t184256 / hacks Goto Github PK

Using hacks as a plugin system with hacks.call(...) dispatcher just begs for setuptools-based plugins registration via entry_points.

Use case:

• A class with several @hacks.into-decorated methods is ready to serve a good job as a plugin.
• An opt-in form of with hacks.use(..., setuptools_autodiscovered=True) enables it.
• CRASH/BURN!

Possible ways:

• flatten call tree within hacks (hurts readability)
• use _call_with_frames_removed convention (is it applicable?)

Allow initializers/deinitializers for hacks.

It seems to be a standard and expected functionlaity for plugin systems.

Execute them in forward order in Registry's enter and in reverse order in exit.

Should I rename enter and exit to hacks_enter and hacks_exit to make hack-grouping objects usable as standalone context managers?