Matan Addam

You are too kind, but I think that reusing windows in testing is a simple, working approach, which overlaps with the philosophy and practice of dependency injection which is anyway...

Just a note to myself that a consequence of `app.event_loop` being a module singleton, is that a pending callback scheduled through `pyglet.clock.schedule_once()` will persevere through the sequence of stopping and...

I worked to prevent my test cases exiting code while any callbacks are left queued, but I think it could be a nice enhancement to either provide (i) a method...

All that said I'd like to share that running headless tests has proven immensely useful and successful for my application, I would not be able to develop and evolve my...

Thanks for those comments. Would [PlatformEventLoop.notify](https://pyglet.readthedocs.io/en/latest/modules/app.html#pyglet.app.PlatformEventLoop.notify) actually be an idiomatic way for syncrhonously clearing all events between pytest tests?

A small side comment ― given the [current implementation regarding `on_draw`](https://groups.google.com/g/pyglet-users/c/wyWCzLYgL1w), if correct, it becomes a little harder to reason about this at present; the callback for `on_draw` will continuously...

Really huge thanks for writing in. I have already accomplished phenomenal things with pyglet. I guess that providing more elastic behaviors like you mention requires a lot of thought and...

Either way I think it will be important to put a large notice about these changes on the release where they are being introduced! it's anyone's choice when to upgrade...

Just about these 3 items, > 1. Pass `None` to `pyglet.app.run(None)`, and it will not internally schedule window draws. > 2. Create `on_draw` handlers as usual. > 3. Call `Window.draw(dt)`...

Just saying this became easier to follow after reading about [shared context](https://pyglet.readthedocs.io/en/latest/programming_guide/context.html#sharing-objects-between-contexts).