[issue36586] multiprocessing.Queue.close doesn't behave as documented

Change by Guido van Rossum : -- stage: -> resolved status: open -> closed ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue36586] multiprocessing.Queue.close doesn't behave as documented

Guido van Rossum added the comment: Closing for lack of activity. -- nosy: +gvanrossum ___ Python tracker ___ ___ Python-bugs-list

[issue36586] multiprocessing.Queue.close doesn't behave as documented

Change by Brett Cannon : -- components: +Library (Lib) nosy: +davin, pitrou ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue36586] multiprocessing.Queue.close doesn't behave as documented

Thomas Grainger added the comment: Should the docs be: > Indicate that no more data will be put on or got from this queue by the > current process. The background thread will quit once it has flushed all > buffered data to the pipe. This is called automatically when the queue is > garbage c

[issue36586] multiprocessing.Queue.close doesn't behave as documented

New submission from Thomas Grainger : The docs for https://docs.python.org/3/library/multiprocessing.html#multiprocessing.Queue.close read: > Indicate that no more data will be put on this queue by the current process. > The background thread will quit once it has flushed all buffered data t