[issue27144] concurrent.futures.as_completed() memory inefficiency

[Will Vousden]

Will Vousden added the comment:

Is there a reason this hasn't been merged yet?

Fixing this bug locally (albeit just by setting Future._result = None when I've extracted the result) reduced the memory footprint of my program from 50 GB to 7 GB, so it seems worth it.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue27144>
_______________________________________