Skip to content

Recommend against creating incomplete stubs #1659

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

Merged
merged 1 commit into from
Oct 10, 2017
Merged

Conversation

JelleZijlstra
Copy link
Member

I disagree with the recommendation that users create incomplete stubs, because such stubs lead to false positive type checker errors (see for example #525). I would like to instead set a norm that all stubs should contain all public objects in the library they cover.

I disagree with the recommendation that users create incomplete stubs, because such stubs lead to false positive type checker errors (see for example #525). I would like to instead set a norm that all stubs should contain all public objects in the library they cover.
@gvanrossum
Copy link
Member

I agree. Typeshed is more mature and we need to set higher standards. I've seen no objections so I'm going to merge this.

At the same time we probably have many modules in typeshed that aren't complete yet. We'll just improve these over time, or occasionally we'll have to decide to cut them.

@gvanrossum gvanrossum merged commit b54a711 into master Oct 10, 2017
@gvanrossum gvanrossum deleted the no-incomplete-stubs branch October 10, 2017 15:27
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

Successfully merging this pull request may close these issues.

2 participants