STINNER Victor added the comment: Martin Panter: > Victor opened Issue 27068 about adding a Popen.detach() method, which such > code could use to opt out of the warning.
I opened the issue because you asked me to open it, but I'm not convinced yet that the design would work. I don't understand yet who is responsible of the pipes for example, especially pipes opened by the Popen object itself (ex: stdout=PIPE), not passed to Popen constructor. It's not as simple as getting a file descriptor as file.detach() or socket.detach(), a Popen object is made of multiple resources (pid and pipes at least). > 2. Revert the warning, and in a future release (e.g. 3.7), add it back along > with a way to opt out of the warning. For this specific issue, the ResourceWarning is correct. I don't understand the use case of explicitly turning this warning off on this specific example? If your output is flooded by ResourceWarning warnings, it's easy to configure Python to ignore them. Example, simplest option: python3 -Wignore script.py. But you are only going to hide a real issue in your code. ResourceWarning exists to help you to reduce your resource consumption. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue29174> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
