Is it necessary to prevent a datasclass field name from being a Python keyword?

I ran into this error when dynamically creating an dataclass:

"Field names must not be keywords: {name!r}"
https://github.com/graphql-python/graphene/blob/master/graphene/pyutils/dataclasses.py#L1196-L1197

The field names come from a defined external dataset, and one field name happens to be a Python keyword, but I don't think that causes any harm.

Start by reading graphene/pyutils/dataclasses.py around lines 1196–1197 and trace how dynamically created dataclass field names are handled. Determine whether rejecting Python keywords is required for this path and define the expected behavior for field names from external datasets before identifying the necessary coverage.

Escrito por el modelo de indexación a partir del texto del issue.