Armin Rigo <[email protected]> added the comment: VYSE: yes, that's possible, but that might be a very bad idea in some cases. It means that if your program leaks FDs heavily, then it would work, but force a complete GC cycle every n'th leaked FDs. The value of n is a constant, but the program can take an arbitrary amount of memory, which makes a complete GC cycle arbitrarily long. The end result is that PyPy would spend an arbitrarily large fraction of its run time in the GC --- slowing down the actual execution, not by 10% nor 100% nor 1000% but by essentially any factor.
I think it's a better idea to go to the individual projects and tell them that they need to close their open files in order to run on any non-CPython implementation of Python. ---------- nosy: +arigo ________________________________________ PyPy bug tracker <[email protected]> <https://bugs.pypy.org/issue878> ________________________________________ _______________________________________________ pypy-issue mailing list [email protected] https://mail.python.org/mailman/listinfo/pypy-issue
