-
Notifications
You must be signed in to change notification settings - Fork 24
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
Conda Generic Plugin Hooks #45
base: main
Are you sure you want to change the base?
Changes from 11 commits
e51c394
9ad8e22
7496dc2
2fbb831
b85a643
4eb363a
3107b9f
760d134
ec6b777
2e5a032
3bc9b8a
3d666b0
dc02b4f
0e350ee
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,218 @@ | ||
<table> | ||
<tr><td> Title </td><td> Conda Generic Plugin Hooks</td> | ||
<tr><td> Status </td><td> Draft </td></tr> | ||
<tr><td> Author(s) </td><td> Full Name <thathaway@anaconda.com></td></tr> | ||
<tr><td> Created </td><td> Dec 22, 2022</td></tr> | ||
<tr><td> Updated </td><td> Dec 22, 2022</td></tr> | ||
<tr><td> Discussion </td><td> _TBD_ </td></tr> | ||
<tr><td> Implementation </td><td> _TBD_ </td></tr> | ||
</table> | ||
|
||
[conda-pre-invoke-location]: https://github.com/conda/conda/blob/48f51e6c1d412270efbbdb1d9ff571087568b6ea/conda/cli/main.py#L69 | ||
[conda-exception-handler]: https://github.com/conda/conda/blob/48f51e6c1d412270efbbdb1d9ff571087568b6ea/conda/exceptions.py#L1120 | ||
|
||
## Abstract | ||
|
||
In order to support a variety of use cases and extensions to conda's default | ||
behavior, we propose a set of generic plugin hooks in this CEP. Included will | ||
be `pre_command` and `post_command` hooks that will allow | ||
plugin authors to execute their plugin code before or after conda commands | ||
run, respectively. Additionally, we introduce the `exception_handler` plugin | ||
hook that will allow plugin authors to override and extend behavior of the | ||
existing [`conda.exceptions.ExceptionHandler`][conda-exception-handler] class. | ||
For each hook, we outline example use cases and | ||
show exactly how plugin authors will define these new hooks. | ||
|
||
## Specification | ||
|
||
This specification calls for the creation of the following three new plugin hooks: | ||
|
||
- `pre_command`: runs before the invoked conda command is run | ||
- `post_command`: runs after the invoked conda command is run | ||
- `exception_handler`: allows overriding or extending the existing | ||
[`conda.exceptions.ExceptionHandler`][conda-exception-handler] | ||
|
||
Below, we discuss an example showing the use of the `pre_command` and `post_command` | ||
hooks together and an example of the `exception_handler` hook. | ||
|
||
### `pre_command` and `post_command` | ||
|
||
Plugin authors create the `pre_command` and `post_command` hooks by first defining a `conda.plugins.hookimpl` | ||
decorated function called either `conda_pre_command` or `conda_post_command` which return either a `CondaPreCommand` | ||
or `CondaPostCommand` class, respectively. These classes will both receive the following three properties: | ||
|
||
- `name`: unique name which identifies this plugin hook | ||
- `action`: a callable which contains the code to be run | ||
- `run_for`: a Python `set` of strings representing the commands this will be run on (e.g. `install` and `create`) | ||
|
||
#### Example | ||
|
||
```python | ||
from conda.plugins import hookimpl, CondaPreCommand, CondaPostCommand | ||
|
||
|
||
PLUGIN_NAME = "custom_plugin" | ||
|
||
|
||
def custom_plugin_pre_command_action(command): | ||
""" | ||
Defines our custom pre-run action which simply prints a message. | ||
""" | ||
print(f"pre-run action before {command}") | ||
|
||
|
||
@hookimpl | ||
def conda_pre_commands(): | ||
""" | ||
Yields our CondaPreCommand instance which attaches our ``custom_plugin_pre_command_action`` | ||
to the "install" and "create" command. | ||
""" | ||
yield CondaPreCommand( | ||
name=f"{PLUGIN_NAME}_pre_command", | ||
action=custom_plugin_pre_command_action, | ||
run_for={"install", "create"} | ||
) | ||
|
||
|
||
def custom_plugin_post_command_action(command): | ||
""" | ||
Defines our custom post-run action which simply prints a message. | ||
""" | ||
print(f"post-run action after {command}") | ||
|
||
|
||
@hookimpl | ||
def conda_post_commands(): | ||
""" | ||
Yields our CondaPreCommand instance which attaches our ``custom_plugin_post_command_action`` to | ||
travishathaway marked this conversation as resolved.
Show resolved
Hide resolved
|
||
the "install" and "create" command. | ||
""" | ||
yield CondaPostCommand( | ||
name=f"{PLUGIN_NAME}_post_command", | ||
action=custom_plugin_post_command_action, | ||
run_for={"install", "create"} | ||
) | ||
``` | ||
|
||
### `exception_handler` | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. can we review, if current implementation of exception classes should be extended to support custom exception handlers? For example - let's say in the code we have (just found the first one)
If I want to write a custom exception handler for his exception, I'm missing context - which environment and reason, why it couldn't be removed (or is conda Context the right thing to use?) If quick question - yes, it worth to review and extend exception handling mechanism - I believe it's another CEP? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. @aovasylenko, please see @jaimergp's comment below. I think he did a reasonable job of summarizing what you were talking about. The scenario you are talking about would require a very extensive refactor to existing code, and I do not think it is realistic anytime soon. In the meantime, it's way easier to just rely on the context object like you said. |
||
|
||
For the `exception_handler` hook, plugin authors begin by defining a `conda.plugins.hookimpl` | ||
decorated function called `conda_exception_handler`. This function will return the | ||
`CondaExceptionHandler` class with the following attributes: | ||
|
||
- `name`: unique name which identifies this plugin hook | ||
- `handler`: a class that is a subclass of [`conda.exceptions.ExceptionHandler`] | ||
|
||
#### Example | ||
|
||
```python | ||
from conda.exceptions import ExceptionHandler | ||
from conda.plugins import hookimpl, CondaExceptionHandler | ||
|
||
PLUGIN_NAME = "custom_plugin" | ||
|
||
|
||
class CustomExceptionHandler(ExceptionHandler): | ||
"""Custom implementation of the ``conda.exceptions.ExceptionHandler``""" | ||
|
||
def handle_exception(self, exc_val, exc_tb): | ||
print( | ||
"Here's a custom message that will show when" | ||
" an exception is encountered!" | ||
) | ||
|
||
super().handle_exception(exc_val, exc_tb) | ||
|
||
|
||
@hookimpl | ||
def conda_on_exception(): | ||
""" | ||
Returns our ``CondaExceptionHandler`` class which attaches our | ||
registers our `` | ||
""" | ||
yield CondaExceptionHandler( | ||
name=f"{PLUGIN_NAME}_exception_handler", | ||
handler=CustomExceptionHandler | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. will it support There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I left that out because I didn't think that this plugin should have that fine grain control. It would also complicate the implementation too. |
||
) | ||
``` | ||
|
||
|
||
## Motivation | ||
|
||
Our immediate motivations for adding these plugin hooks include the following: | ||
|
||
### Better authentication handling | ||
|
||
The `pre_command` hook will enable plugin authors to interrupt the normal start up of conda commands. | ||
For better authentication handling, this opens the door for either asking the user directly | ||
for their credentials or retrieving credentials from an OS keyring. These credentials can | ||
then be stored and used for the duration of the running command and subsequent runs too. | ||
|
||
A prototype of how this could function can be found in the following pull request: | ||
|
||
- https://github.com/conda/conda/pull/12139 | ||
|
||
### Better exception logging | ||
|
||
The `exception_handler` hook will enable plugin authors to provide a better experience for | ||
users and developers when exceptions are encountered. For example, a plugin could be written | ||
to display stacktraces in color or even drop you into a debugging console. | ||
|
||
### Plus more | ||
|
||
The above use cases are just a few possibilities out there. We know that our users and | ||
community will have many more ideas for how best to utilize these generic plugin hooks. | ||
|
||
## Rationale | ||
|
||
By introducing a set of generic hooks like the above, we grant plugin authors with quite a bit of | ||
flexibility for customizing how conda behaves. We believe starting out with a small set of generic | ||
plugin hooks is best so that we do not overwhelm would-be conda plugin authors. Depending on | ||
how much these plugin hooks are used and whether there is a demand, we may choose add more in | ||
the future with a new CEP. For now though, we believe it is best to stick with this narrow | ||
selection as we slowly grow our plugin ecosystem. | ||
|
||
## FAQ | ||
|
||
- Will I have access to global variables such as `conda.base.context.context` in my plugin hook? | ||
- Yes, for all plugin hooks listed in this CEP, they will be placed after the global context | ||
object has been initialized. | ||
|
||
- Where exactly will the `pre_command` hooks be called? | ||
- All registered `pre_command` hooks will be called before the `do_call` call in the | ||
[`conda.cli.main:main_subshell`][conda-pre-invoke-location] function. | ||
|
||
- Where exactly will the `post_command` hooks be called? | ||
- All registered `post_command` hooks will be called after the `do_call` call in the | ||
[`conda.cli.main:main_subshell`][conda-pre-invoke-location] function. | ||
|
||
- Which methods should I override on the exception class to customize behavior? | ||
- The primary method will be `handle_exception` but others are available too: | ||
- `handle_application_exception` called for: | ||
- `CondaError` and it's subclasses | ||
- `EnvironmentError` | ||
- `MemoryError` | ||
- `KeyboardInterrupt` | ||
- `SystemExit` | ||
- `handle_unexpected_exception` called for all other exceptions | ||
|
||
- Will these hooks be available for `conda activate` and `conda deactivate` commands? | ||
- Initially, no. But, if there is demand for this we will reconsider making these generics | ||
available for these two commands. The reason for this is the slightly different way these | ||
commands are handled versus others. Their implementation is tightly coupled to the shell | ||
of the current user and adequately handling this use case would be more complex than what | ||
we are currently prepared to implement. | ||
|
||
- Will I be able to combine the use of these hooks with others in a single plugin? | ||
- Yes! We want to create a rich set of plugin hooks to allow authors a variety of possibilities | ||
for extending conda. We believe the true power of these generics will show when they are | ||
combined with existing plugin hooks. | ||
|
||
|
||
## Resolution | ||
|
||
_TBD_ | ||
|
||
## Copyright | ||
|
||
All CEPs are explicitly [CC0 1.0 Universal](https://creativecommons.org/publicdomain/zero/1.0/). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
is it optional or mandatory parameter?
(also asked similar question if exception handler hook should have it as well)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good question. I think making this argument optional with the default behavior of it running for every command makes the most sense.