According to this comment in the requests project:
We deliberately allow any mapping type to allow for a variety of use-cases. A change here won't be accepted
I think this means that the strict typing shown here is not correct:
https://github.com/python/typeshed/blob/main/stubs/requests/requests/sessions.pyi#L116
And instead something that satisfies a mutableMapping would be more correct?
The X to my Y problem is that I am very much used to working with .headers set to a built-in dict. And if it works and is supported by requests , could I submit a patch to the type stubs? Satisfying this typing constraint as it is right now feels incorrect given the long history of the dict() being sufficient.
According to this comment in the requests project:
I think this means that the strict typing shown here is not correct:
https://github.com/python/typeshed/blob/main/stubs/requests/requests/sessions.pyi#L116
And instead something that satisfies a mutableMapping would be more correct?
The X to my Y problem is that I am very much used to working with
.headersset to a built-in dict. And if it works and is supported byrequests, could I submit a patch to the type stubs? Satisfying this typing constraint as it is right now feels incorrect given the long history of the dict() being sufficient.