This seems quite fragile. Personally I would just ignore it in typeshed. In general, stubtest isn't meant to work perfectly in every possible situation, which is why the exclude lists exist.

I agree with @Akuli, I don't think we should add this kind of module-specific logic.

This seems quite fragile. Personally I would just ignore it in typeshed. In general, stubtest isn't meant to work perfectly in every possible situation, which is why the exclude lists exist.

Well, I understand that, but after I've made this fix, stubtest found 4 more errors in my OpenSSL.crypto stubs, which seems useful and would not happen if stubtest was left unfixed.

This will become unnecessary in the future when module-level __getattr__ (in .py files) becomes a thing. It can be used to implemented deprecated module members, and there's no longer any need for libraries to wrap the module in a custom class.

That future is here as of Python 3.7, for what it's worth.

But pyopenssl still supports Python 2 (eww) and 3.6. https://github.com/pyca/pyopenssl/blob/main/setup.py

value is a very common attribute name and this could cause some confusing things to happen.

I see this would not be merged, but just in case, I've provided a more explicit check excluding any vagueness.