Maximilian Hils

We could possibly adapt something like this: https://github.com/pyca/pyopenssl/blob/main/tests/test_ssl.py#L2837 If that's easy to add I'm all for it, but I also feel that not having an elaborate test here is not...

Anecdotally we've had some people request this for mitmproxy (https://github.com/mitmproxy/mitmproxy/issues/5449 and https://github.com/mitmproxy/mitmproxy/pull/5698), but I don't have hard numbers. Do we know which pyOpenSSL/cryptography release disabled insecure renegotiation? CHANGELOG.rst isn't conclusive...

https://www.openssl.org/news/cl30.txt says it's OpenSSL 3.0, so that means cryptography 37 (2022-04-26).

I absolutely agree that this is a useful feature, but I'm don't necessarily think it's something that should be natively supported by pdoc. Here's what I would do instead: 1....

@dAnjou: For your specific use case, it's probably easier to do the "check out another version" part in a bash script and then invoke your `make-docs.py` script from there. Having...

> I don't think it matters whether I check out the version in a bash script or in the Python script. Well the idea would be that you have a...

This feels more like a hack than anything else, but given that it's in PEP 484 I'd be happy to merge a PR that adds support for it. Fwiw, a...

Sorry this took so long! I've finally found some time do do a deep dive here and refactor things a bit. Does this look good to you now?

This looks like an issue in the Markdown library we're using, [markdown2](https://pypi.org/project/markdown2/).

Contributions are welcome here, the relevant code is in https://github.com/mitmproxy/pdoc/blob/main/pdoc/docstrings.py. :) That being said, my general take here is that type info should live in the type annotation, and then...