Skip to content
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

Plugin support #36

Open
jakirkham opened this issue Jun 23, 2017 · 2 comments
Open

Plugin support #36

jakirkham opened this issue Jun 23, 2017 · 2 comments

Comments

@jakirkham
Copy link
Owner

Would be good if this could support different launching methods that could be described in some plugin directory. Presumably this would be a package in the library. This could include some standard ones like SGE, LSF, MPI, DRMAA, multiprocessing, etc. as built-ins. However users could easily make others that are not supported and have them installed here too. Thus this package would detect available plugins at runtime. A subcommand could be used to specify which launcher to prefer (e.g. splauncher sge <...>). If one isn't specified, there could be a hidden directory in the user's home directory, which would specify the order to check/try. Can probably borrow some lessons learned from ipyparallel to inform how to do this.

@jakirkham
Copy link
Owner Author

Would add additional plugins could be added in the user's configuration directory. That way if they have some custom changes to the standard plugins, they can provide them there.

@jakirkham
Copy link
Owner Author

Was hoping to get a deprecation into this release to start this process. However it doesn't look like we have time. So going to punt on this for now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant