is_member_of_type about typing_inspect HOT 6 CLOSED

@lucaswiman Before you start with this approach, please note that I already did exactly this work. Including support for type variables. Including issubtype. Already supporting older versions of typing module, at least from 3.5.2.2 onwards. Tested with Python 2.7, 3.5, 3.6, 3.6.1 and even Jython.

Implementing this was much more involved than one might expect (e.g. getting things like issubtype(Tuple[int, int, int], Iterable[int]) right.) Honestly NamedTuple is not yet supported, but it is on the agenda. Maybe you could at first try, if the existing approach might be already sufficient (see https://github.com/Stewori/pytypes#is_of_typeobj-cls). If it's not, maybe we can combine our efforts and improve it...?

from typing_inspect.

No, that looks fantastic! I searched for something which implements that collection of functionality, and could only find runtime typecheckers.

In the abstract, I think much of your pytypes library would be better in the standard library (or at least linked from the typing documentation), but for my particular interests, your library looks great!

from typing_inspect.

In the abstract, I think much of your pytypes library would be better in the standard library

Having read through the documentation in more detail, I guess only a small subset of it makes sense for the standard library, though several of the "Utilities" functions would be good candidates.

from typing_inspect.

After some thinking, it seems to me this should not be in typing_inspect, mainly because it is hard to draw a line between "simple" and "non-simple" runtime checks. Plus there are excellent existing tools mentioned above.

Anyway, thanks for a nice write-up!

from typing_inspect.

That's disappointing; I do hope you'll reconsider after the typing library matures. Obviously missing functionality in the standard library leads to a proliferation of incompatible third party libraries of varying quality (c.f. the history of urllib2, requests, etc. where "simple" functionality has a complicated answer as to what you should use.) Python has always advertised itself as "batteries included", and this seems like a glaringly missing battery.

From the perspective of an end user of typing it feels like isinstance is broken, and there's no functionality to replace it. Once pytypes is released on pypi, linking to it in the typing docs would help fill this gap.

Plus there are excellent existing tools mentioned above.

pytypes hasn't been released on pypi and the other tools I could find did not implement this functionality in a simple form, so I disagree with you there. It may be the case in the future, but I don't think it is the case now.

from typing_inspect.

pytypes hasn't been released on pypi and the other tools I could find did not implement this functionality in a simple form, so I disagree with you there. It may be the case in the future, but I don't think it is the case now.

I would say that this is a perfect reason for you to contribute to and improve these projects, so that they will suit your needs. The goal they declare seems to be what you need, while the main goal of typing_inspect is mostly runtime introspection of types themselves.

from typing_inspect.