Stefan Richthofer

No, it actually does not get rid of ``_ForwardRef``. After looking more closely into ``_ForwardRef`` I had learned that it provides fields to store the referenced type, i.e. ``__forward_arg__``, ``__forward_value__``...

This is not an error, but your ``__init__`` is a type-incompatible override. Even without ``@override`` decorator pytypes also checks against the types of parent methods. This allows you to only...

Maybe this shoud be configurable for each method individually as an optional arg to ``typechecked``. At least I consider if it should exclude ``__init__`` because of the reasons explianed in...

Given that you mentioned adding args to ``__init__`` and it looks like you are using ``super`` in ``__init__`` I remember the following article I'd like to forward to you: [Python's...

Not a solution as this is actually a symptom of pytypes being unaware of `ignore`: You can work around this by setting `pytypes.strict_annotation_collision_check = False`.

Ah, sorry; I recognized that this workaround wouldn't do it because pytypes still asserts that a concurrent type string to a type annotation would yield the same type. It would...

Do you know under what circumstances that happens? Do you have a code snippet to reproduce? I just ask to figure out what behavior should be applied then...

We'll need to find a workaround. Any idea how to find the module that hosts the function in such a case? What about using [``pytypes.util.getmodule``](https://github.com/Stewori/pytypes/blob/master/pytypes/util.py#L548) on ``function.__code__``? Or is ``__code__``...

So, the trick with ``co_filename`` seems not to be workable. Still, attrs-generated methods might still allow to identify the module somehow (finally they *are* hosted in some module, arent't they?)....

Is ``__qualname__`` available for generated methods? (this wouldn't solve it for Python 2 unless something similar would be available there too)