Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings

Evaluate ways to determine accuracy and reduce incomplete type stubs #8481

Copy link
Copy link
Closed as not planned
@kkirsche

Description

@kkirsche
Issue body actions

I've reached out to psf/requests via their issue tracker (psf/requests#6211) to begin exploring why various projects aren't merging the type stubs from typeshed.

From requests, they've said that previous reviews of the type stubs are inaccurate and prevent them from merging the type hints into the main codebase.

This issue is to explore how type stub accuracy can be better evaluated to reduce the maintenance burden currently imposed on typeshed caused by inaccuracy or incompleteness.

Ultimately, while having stubs may help end users in the short term, inaccurate or incomplete stubs can prevent or delay long term adoption by the upstream team(s).

Metadata

Metadata

Assignees

No one assigned

    Labels

    project: policyOrganization of the typeshed projectOrganization of the typeshed project

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      Morty Proxy This is a proxified and sanitized view of the page, visit original site.