Duprat

> I've removed @YvesDup's tests `test_shutdown_all_methods_in_one_task`, `test_shutdown_putters_deque`, `test_shutdown_getters_deque`, `test_shutdown_get`, `test_shutdown_get_task_done_join`, and `test_shutdown_put`, and replaced them with simpler and lower-level tests. Are there any scenarios I've missed? I agree with all...

All tests run good. But, I am wondering whether it's not easier to understand test aims when they are organized by features like: + `test_shutdown_get[_task_done]`, + `test_shutdown_put`, + `test_shutdown_join`, +...

> > With your actual organization (`test_shutdown_empty`, `test_shutdown_nonempty`), its seems to me harder to follow the test purposes. It'is up to you. > > Each test is a different scenario,...

> in both cases the task should raise `ShutDown`: when the queue is empty, there should be no distinction between immediate and non-immediate shutdown (ignoring unfinished-tasks). @EpicWink , there is...

> > there is the same bug on threading queue shutdown. I will open an issue. > > @YvesDup I've created issue #117531, and fix in PR #117532 I have...