Mistakes have been made

Am I beginning to experience a small part of the reason why blind and low vision users seem to prefer Windows?

you made the right choice not trying to caption it. 😮

Wow. I'll never read RFC 2119 the same way again (sadly, yes, I have read it multiple times).

I suspect the "over-the-top sarcastic, passive-aggressive, condescending" reading might not suite Strype. I wonder how versatile the voice actor is.

I notice in the source code there's type information (as a comment beneath method definitions) but that doesn't make it to the documentation, is that a conscious decision? Python docs aren't very consistent about this, but I personally prefer to see the expected types.

Those are nice docs! I couldn't find them linked from strype.org either, might be worth adding them somewhere on the landing page?

I'd be more than happy to review the API surface and make some proposals. I'm not a Python API expert, but I have written a fair amount of Python.

Is there an easy way to view the API surface for the graphics (media?) API?

The example you give of a sound literal constructor feels like it could be solved by having a single constructor with a sound argument that has a default value of None?

If the argument is not set, you get an empty sound.

This is very cool! FYI, the Newcastle and Manchester events don't appear to be listed on the Strype events page.

Gimme gimme

We surely don't want all debugging code committed to the VCS, but it feels like there's a design space for ephemeral/one-time debugging logic vs longer lived debugging logic that could be explored with richer tools.

This could extend quite naturally to debug profiles, such that the code can remain, and even be committed to the VCS, but only be executed when you're in the debugging profile.

There's also now a George Bool statue at Lincoln Central train station

Enjoyed that. Thanks!

🛹