Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

The PEP should clarify the status of typing vs. types #8

Closed
gvanrossum opened this issue Oct 16, 2014 · 3 comments
Closed

The PEP should clarify the status of typing vs. types #8

gvanrossum opened this issue Oct 16, 2014 · 3 comments

Comments

@gvanrossum
Copy link
Member

Lukasz wrote:

  • 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.
@ambv
Copy link
Contributor

ambv commented Jan 8, 2015

Ignored this issue for now: don't know yet.

@gvanrossum
Copy link
Member Author

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.

@gvanrossum
Copy link
Member Author

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?)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants