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
If I'm not mistaken, using track() anywhere in the same process means that now all of your tempfiles will get automatically deleted prior to process exit, even in those parts of the program that never intended to remove temporary files. This could affect the mode of operation of any dependencies that happen to also use temp.
Also that one can not use cleanup() without having called track() is IMHO an unwarranted complication. I fail to see what the relevance of this for long-running processes is; if anything, you do want to reliably unlink temporary files in such processes as soon as they're not needed to reduce chances of filling up the disk.
The text was updated successfully, but these errors were encountered:
If I'm not mistaken, using
track()
anywhere in the same process means that now all of your tempfiles will get automatically deleted prior to process exit, even in those parts of the program that never intended to remove temporary files. This could affect the mode of operation of any dependencies that happen to also usetemp
.Also that one can not use
cleanup()
without having calledtrack()
is IMHO an unwarranted complication. I fail to see what the relevance of this for long-running processes is; if anything, you do want to reliably unlink temporary files in such processes as soon as they're not needed to reduce chances of filling up the disk.The text was updated successfully, but these errors were encountered: