Glyph

As a fellow beleaguered open source maintainer I don't want to hassle you @BenziAhamed , but I can confirm that this fixes the issue and I'd love to get it...

looks like github actions has upgraded so this is a blocker now

@cjwatson fix is in review if you want to give it a look

> That said, I'm leaving this issue open until I've ported py2app to Python 3.14. I'm hoping to get there this weekend... Thanks so much for looking at this, and...

> Another option is to update the `Key.verify()` signature to 1. This is obviously incompatible if done as described; presumably you mean `expectedAlgName=None`? 2. Could we do something more readable?...

Actually, maybe rather than a cleanup/type-safe thing, consistency would be better. I think `sign()` calls this parameter `signatureType`, and it's exactly the same, even with a similar infer-the-right-one step. Could...

I think that this should remain open; it's not quite analogous to TLS, because: - TLS's peculiar state transition is from "certificate state not initialized yet" to "certificate state is...

The simplest, most compatible thing that we could do for the moment is to add a flag to the endpoint (and string syntax) like: `clientFromString(reactor, "tcp:host=127.0.0.1:port=2000:connect=deferred")` , where `connect=immediate` would...

The goal with not adding these plugin types was to gently guide people away from using strports.listen directly, and towards serverFromString / clientFromString. You can tell it’s old and unfortunate...

> I think that we should add this functionality to help Buildbot users. I would much prefer it if we could fix this in Buildbot rather than twisted, because fixing...