-
Notifications
You must be signed in to change notification settings - Fork 155
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
[Request] Allow plugins as Python modules #537
Comments
What would also be useful is to tell decky to just start and stop a binary, as I mainly just have a native backend and use websockets to communicate. This would completely eliminate the need for a python file in general if you don't want one |
But yes op makes a good point and is a better plan than the current py_modules thing |
It seems for module backends, all that really needs changing is this line here |
Well, depending on how importlib handles things it may need to be the |
Importlib handles it like the core import The module name could be made configurable but one step at a time |
Yeah, that line seems to be the only change really needed |
Feel free to pr if you like |
Enough feedback on the Discord has convinced me that this isn't worthwhile. |
Please confirm
Feature Request Description
Decky Plugins should also be usable as a python module
Further Description
Right now plugins are mainly loaded via a main.py
A module would allow proper encapsulation of the code as well as allow specifying relevant information in multiple ways that are query able through official means (the pkg_resources library).
Modules would also allow the creation of wheels, which can be used to bundle dependencies of various kind.
The text was updated successfully, but these errors were encountered: