> I think previously we had discussed a resource manager type design that would
> try to catch crashes/errors and restore the initial state. Was that idea
> rejected for some reason?
Not rejected, but ... scheduled for a later date.
With all the things happening, I wanted to fix the most annoying problem first.
The 'architecture' of network.py makes any major refactor a significant undertaking. I don't know if it's of the highest priority.
> I think previously we had discussed a resource manager type design that would
> try to catch crashes/errors and restore the initial state. Was that idea
> rejected for some reason?
Not rejected, but ... scheduled for a later date.
With all the things happening, I wanted to fix the most annoying problem first.
The 'architecture' of network.py makes any major refactor a significant undertaking. I don't know if it's of the highest priority.