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

Make it possible to use entry points to register DLite plugins #927

Open
jesper-friis opened this issue Aug 15, 2024 · 0 comments
Open

Make it possible to use entry points to register DLite plugins #927

jesper-friis opened this issue Aug 15, 2024 · 0 comments

Comments

@jesper-friis
Copy link
Collaborator

Currently, when someone creates a package that provides a new data model or plugin, users of that package has to either set environment variables or call one of the following functions:

dlite.storage_path.append(...)         # add search path for new data models
dlite.python_storage_plugin_path(...)  # add search path for new storage plugins written in C
dlite.python_mapping_plugin_path(...)  # add search path for new mapping plugins written in C
dlite.storage_plugin_path(...)         # add search path for new storage plugins written in Python
dlite.mapping_plugin_path(...)         # add search path for new mapping plugins written in Python

An alternative, and in most cases preferable solution, would be to allow packages providing DLite plugins to register them using entry points.

This issue is about implementing entry points covering these cases.

@jesper-friis jesper-friis linked a pull request Sep 12, 2024 that will close this issue
15 tasks
@jesper-friis jesper-friis removed a link to a pull request Sep 12, 2024
15 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant