Skip to content

Add fundamental types to resolvers #1959

@flying-sheep

Description

@flying-sheep

seems like the actual types that define Python behavior like collections.abc.Mapping are missing from the default resolvers, and instead some random collection of builtin types is there:

I say “random” because MappingProxyType, KeysView, … are just as fundamental Python types that are used whenever something as basic as a class is encountered so I can’t think of a reason why they shouldn’t be there when dict is, let alone some Django classes and other stuff!

But as initially said: Python’s behavior is actually defined by collections.abc.* classes, so instead of having random builtin sequences like list, frozenset, … in the defaults, why not just use collections.abc.{Sequence,Mapping,Set} directly?

PS: #825 was closed because its title asked about this being possible. I know it’s possible and ask for it to be changed instead.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions