You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The remark about removing types from being mentioned actually
makes me think we could solve many issues before they arise by
introducing a short section The place of the typing module in
the standard library which would explain how the authors intend for
it to be used and what is its role compared to builtin types, types, collections, and collections.abc. The worries
that Guido has about the types module being ill-suited for type
hinted are spot on, we should mention that in the document.
The text was updated successfully, but these errors were encountered:
Isn't this all pretty clear now? We should just downplay types.py -- it only defines concrete types. But we could easily have a stub for it if mypy has trouble understanding its highly dynamic approach.
I think we need no more edits for this topic. typing is mentioned exactly once and in an appropriate fashion (types defined there are acceptable). (@jukka -- is there mypy work needed to implement this?)
Lukasz wrote:
types
from being mentioned actuallymakes me think we could solve many issues before they arise by
introducing a short section The place of the
typing
module inthe standard library which would explain how the authors intend for
it to be used and what is its role compared to builtin types,
types
,collections
, andcollections.abc
. The worriesthat Guido has about the
types
module being ill-suited for typehinted are spot on, we should mention that in the document.
The text was updated successfully, but these errors were encountered: