Josh Rosenberg added the comment: The Pool workers are created eagerly, not lazily. That is, the fork occurs before map is called, and Python can't know that the objects passed as arguments were inherited in the first place (since they could be created after the Pool was created). If you created worker tasks lazily, then sure, you could fork and use the objects that are inherited, but that's not how Pools work, and they can't work like that if the worker processes process more than one input without eagerly evaluating input sequences (which would introduce other problems).
---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue23979> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
