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

feature: non-context-manager-based access to the Golem engine #561

Closed
shadeofblue opened this issue Jul 26, 2021 · 0 comments · Fixed by #644
Closed

feature: non-context-manager-based access to the Golem engine #561

shadeofblue opened this issue Jul 26, 2021 · 0 comments · Fixed by #644

Comments

@shadeofblue
Copy link
Contributor

shadeofblue commented Jul 26, 2021

to allow more freedom in the usage of the Golem engine, there should be an easy way to instantiate Golem and to be able to explicitly shut it down, without having to use the context manager syntax.

additional thoughts:

  • maybe there could be an option to automatically close Golem when e.g. nothing else is done with it? (e.g. on no explicit close by the time the program exists or when Golem instance leaves the scope) -> e.g. __del__ implementation or an atexit handler
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants