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.

Sign up for GitHub

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

Jump to bottom

Load plugins in a separate namespace #950

Closed
jesper-friis opened this issue Sep 16, 2024 · 0 comments · Fixed by #953
Closed

Load plugins in a separate namespace #950

jesper-friis opened this issue Sep 16, 2024 · 0 comments · Fixed by #953

Comments

@jesper-friis
Copy link
Collaborator

Now when DLite might load the plugins with the calling interpreter, it should not touch the __main__ namespace. Create a separate namespace/scope that the plugins are loaded and evaluated in.

If the plugins get their own scope when loaded, we can also avoid surprising cross-interactions between plugins.
@jesper-friis jesper-friis changed the title Evaluate plugins in a separate namespace Load plugins in a separate namespace Sep 16, 2024
@jesper-friis jesper-friis linked a pull request Sep 27, 2024 that will close this issue
950 load plugins in a separate namespace #953
Merged
9 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

950 load plugins in a separate namespace SINTEF/dlite
1 participant
@jesper-friis