Stefan Richthofer

@JelleZijlstra is that backwards compatible, even to Python 3.6? I suspect one might better write ``` typing_inspect.get_origin(tp) in {list, List} ```

I encountered the same issue on supporting Python 3.7 in pytypes. I tried to resolve it by an internal map, e.g. ``origin_dict[collections.abc.Iterable] == typing.Iterable`` but discarded that because it only...

Looking at the changes, that does not seem to address the issue discussed here, nor the somewhat related issue I have with getting the generic base type. Correct me if...

Okay, then "normalization" refers exactly to the opposite of what is desired in this issue. One would need a way to opt out of the normalization.

Maybe [pytypes.get_arg_for_TypeVar(typevar, generic)](https://github.com/Stewori/pytypes#get_arg_for_typevartypevar-generic) is what you are looking for.

Feel free to make a PR for that ;) (Edit: I really hope to be able to provide Python 3.7 support for pytypes. Still I found it important to cross-link...

For the record. In a recent commit I fixed workability of ``pytypes.get_Generic_parameters`` for Python 3.7 (however, not released). It can now be used like this: ``` T = TypeVar("T") class...

It looks like this is defined in ``default.css`` as ``` /* line 147, ../scss/default.scss */ slides > slide:not(.nobackground):after { font-size: 12pt; content: attr(data-slide-num) "/" attr(data-total-slides); position: absolute; bottom: 20px; right:...

If I directly modify ``_build/slides/_static/theme/css/default.css`` like this: ``` /* line 147, ../scss/default.scss */ slides > slide:not(.nobackground):after { font-size: 12pt; /* content: attr(data-slide-num) "/" attr(data-total-slides); */ position: absolute; bottom: 20px; right:...

So far I miss tests here that scope the case that type information in hosted in stubfiles, which are clearly and officially part of PEP 484 specification. Also, no tests...