I think this advocates a certain style of concurrency rather than a particular language feature. As hinted at in the article, nothing prevents me from spawning

I think this advocates a certain style of concurrency rather than a particular language feature. As hinted at in the article, nothing prevents me from spawning a global_nursery at the top of my entry point and making that visible everywhere. I can still use this global_nursery (or any other higher-level one) to break resource cleanup. I do find the argument compelling. But Python is simply too powerful for this abstraction to work perfectly, you’d need further restrictions. Maybe something like linear types (or Rust’s borrow checker) to make sure local state doesn’t escape into global nurseries?