Skip to content

Use latest stubtest from git in CI #7305

Closed
@hauntsaninja

Description

@hauntsaninja

There have been a number of great additions to stubtest recently. Several of these introduce new errors in typeshed. This means whenever we next update stubtest, there'll be a large backlog of allowlist adjustments or regression fixes — often duplicating work done when validating the change to stubtest. Lack of support for submodules in VERSIONS has also recently confused two contributors.

When stubtest was new, we used to install it from git (with a pinned hash) and this let us iterate quickly (and before that, for the longest time, we used to run all of mypy unpinned from latest git master). The only real downside of this is that stubtest is marginally (not too noticeably) slower. If we really cared about speed, we could install from https://github.com/mypyc/mypy_mypyc-wheels.

There've been about ten commits to stubtest since 0.930, we can upgrade commits one by one if necessary.

cc @AlexWaygood (if this is something you'd be interested in!)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions