Benjamin

Implemented via https://github.com/pyglet/pyglet/pull/434

That looks like a good plan. Your logic looks sound.

> @pushfoo > > ``` > frozen + mutable # creates a new frozen > mutable + frozen # creates a new mutable > ``` > > Why should these...

> > ``` > > frozen += frozen # raises AttributeError > > frozen += mutable # raises AttributeError > > ``` > > Why not have these be equivalent...

Hi, In general, OpenGL doesn't really work well with multithreading. You should try to perform all drawing operations from the main thread, and only use threads for logic calculation, or...

Unfortunately there isn't any way to fix is in pyglet. The OpenGL drivers all behave slightly differently across platforms, and they do not work well with multithreading in general.

Hi, The last post in that thread seems like the correct answer. Try that with the latest pyglet. It's not recommended to use pyglet 1.2.4 since it's long long out...

I'll close this for now as seems there is a solution, but please follow up (or open a new ticket) if you would like to discuss it further.

Hi Tom, We have already started adding basic type hints to the public facing APIs in the master (v2.0) branch. It's really just a matter of someone taking on the...

Interesting, I was unaware that Windows had that limitation with tempfiles. Maybe the easiest solution would just be to move the close logic into `__del__` for the FFMpegSource? ```py def...