-
Notifications
You must be signed in to change notification settings - Fork 94
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
plugins: xtriggers #3456
Comments
Additional information: At present the Xtrigger location logic is here: cylc-flow/cylc/flow/subprocpool.py Lines 39 to 66 in c86e3c5
This is the logic which needs adjusting to use package metadata instead of the From Riot discussions:
To close this issue (the Cylc Flow side of things)
Further work to be undertaken in the cylc/cylc-xtriggers repo. |
Closed by #5831 |
Part of #2959
Blocked by: #3497, #4106
Implement our first extension point for Xtriggers.
Problem
At present we have Xtriggers provided by two sources:
Cylc Flow
cylc.flow.xtriggers
Cylc Xtriggers
cylc.flow.xtriggers
So we have the
cylc.flow.xtriggers
module defined in two places which I think won't work as Python is surely just going to return the firstcylc.flow.xtriggers
module it finds?cylc.flow.xtriggers.__file__
can only resolve to one location.Proposal
Use package metadata to register Xtriggers in the manner outlined in #2995
This way we can locate them using
pkg_resources
rather than by namespace.At the Cylc Flow end this means:
pkg_resources
to locate Xtriggers rather than attempting to import them fromcylc.flow.xtriggers
directly.Pull requests welcome!
The text was updated successfully, but these errors were encountered: