Adding type hints to class level in SwaggerClient subclass

[voneiden]

Would there be any unwanted side effects in adding type annotations to the class level in the template?

bravado-types/bravado_types/templates/module.pyi.mako

Line 35 in d5f0aa6

class ${config.client_type}(bravado.client.SwaggerClient):

class ${config.client_type}(bravado.client.SwaggerClient):
% for resource in spec.resources:
    ${resource.name}: ${config.resource_type(resource.name)}
% endfor
    def __init__(self, swagger_spec: bravado_core.spec.Spec,
                 also_return_response: bool = False) -> None:

Backstory: It seems Intellij based editors fail to register types defined in subclass init method unless a value is assigned.

[nickgaya]

This project uses MyPy as the reference type-checker. I believe my original intent with declaring the attributes inside the __init__ method is to mark them as instance attributes that should not be accessed via the class. But since MyPy does not distinguish between these (see python/mypy#240), I would be fine with moving these declarations to the class level for greater compatibility with IntelliJ.

However I am no longer actively maintaining this project, and many of the tests are now failing which would need to be fixed before adding any new features.

[voneiden]

However I am no longer actively maintaining this project, and many of the tests are now failing which would need to be fixed before adding any new features.

Understandable. Bravado itself seems to be going a bit slow too. Say, as an expert of sorts in this area, is there any alternative you would advocate today to achieve similar results? Just swagger codegen?