Benjamin

Thanks for pointing that out. I'll have a look at the file. I would like to add support for .gox files to my project at some point, since it's easier...

Sorry this has gone so long without attention. I'd be happy to have documentation contributions if something can be improved.

Thanks for opening the ticket, and I'm glad you're enjoying esper. Can I ask why it's important that entities have the same ID after loading? The proposed patch would work,...

Sorry for leaving this hanging for so long. I think for the main Esper releases I want to keep it as-is, just for performance reasons (even if very small). That...

Thanks for opening the ticket, and for the suggestion. For the EventDispatcher subclasses, you pointed out how the subclass methods are called separately and not just added to the `_event_stack`....

For breaking changes, the policy has been to deprecate changes for one release cycle, then remove in the next. Currently, however, we're in a bit of a transitional period since...

For priorities, if the stack behaved like a heap (could probably *be* a heap internally), then you could do stuff like pushing a handler to any position in the stack...

The way I could see it working is like this: If all handlers default to `priority=0`, then they would be invoked in the order in which they were added. The...

> Just to note, the current order of handlers is the opposite: the last added handler is invoked first. I don't have any preferences about this, just wanted to point...

I mentioned the policy in a previous reply: https://github.com/pyglet/pyglet/issues/205#issuecomment-633492614 It would be best to target this for 2.0, since we can't make breaking changes in the 1.X series at this...