You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi @wyli, you are right, it has been there from before. The issue comes from the test when using tifffile with LoadImage since LoadImage has first select the reader and create the object and then use the object separately. This mean that the image object is not being closed. I will submit a PR to fix this in LoadImage.
Activity
bhashemian commentedon Nov 3, 2022
Hi @wyli, you are right, it has been there from before. The issue comes from the test when using tifffile with
LoadImagesinceLoadImagehas first select the reader and create the object and then use the object separately. This mean that the image object is not being closed. I will submit a PR to fix this inLoadImage.bhashemian commentedon Nov 14, 2022
Closed as it is only a warning and happens in a specific situation so it is not worth to change the API for it.
wyli commentedon Nov 14, 2022
this is not addressed yet, I think we keep this open so the other contributors may provide a good solution.
pruthvi-3417 commentedon Jun 3, 2026
Hi, I would like to work on this issue. I am currently investigating the source of the unclosed file warning and will update with my findings.
vishnukannaujia commentedon Jun 15, 2026
I'd like to take this — PR incoming.
Force GC in WSIReader tests to suppress ResourceWarning for unclosed …