Kevin Paul

@jacobtomlinson: Yeah. I was thinking of something like: ```python with MPICluster(...) as cluster, Client(cluster) as c: if cluster.is_client(): ... ``` where the `MPICluster(...)` object would essentially be the `initialize(...)` method,...

Yeah. If you have time for a PR, that would be great, @evgri243!

@YJHMITWEB: You are proposing that `comm=None` (the current default) be entirely disallowed, even though it works in many setups. This seems a bit restrictive to me. Is it fair to...

Another modification that I might be in favor of is keep the current design but detect the `comm.get_size()` after the internal `comm` is created (i.e., in the `comm=None` case). If...

These are errors I've seen before. I can't remember what is going on right now, but I'll look into it when I'm back in the office in a week. Sorry...

@lgarrison: I have not, yet. I'm sorry. This week got very messy. I absolutely _will_ look into this on Monday. I'm sorry for the delay.

@lgarrison: I've verified the error on both Ubuntu and Rocky Linux. This is actually a resurgence of #88, which notes exactly the issue that you are seeing. I had thought...

(Note that #89 actually changed the `atexit`-called `send_close_signal` function to be exactly what @jacobtomlinson suggested you try, namely `client.shutdown()`.)

...And I can further verify that these `CommClosedErrors` occur even for Python 3.10.6, on Linux and Windows.

Due to the problems noted in #88 related to errors occurring during shutdown _not_ resulting in non-0 exit codes, the PyTest suite is not catching errors. I think this is...