-
Notifications
You must be signed in to change notification settings - Fork 126
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
ThreadPool not closed #16
Comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Love this project! A small issue: in mesh.py the ThreadPool is not closed, resulting in the following warning when running under pytest
ResourceWarning: unclosed running multiprocessing pool <multiprocessing.pool.ThreadPool state=RUN pool_size=1>
This can be avoided by using the pool under the context management protocol
with ThreadPool(workers) as pool:
The text was updated successfully, but these errors were encountered: