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

Sign up
Appearance settings

Discussion: Upgrade repo version after a release to dev to not match release version #528

Open
@Daraan

Description

A while ago to do some tests I wanted to upgrade my current typing_extensions version to the current GitHub version by using
pip install git+https://github.com/python/typing_extensions.git.

I also blame pip here because it does not tell that it doesn't install anything. pip did not perform an upgrade because the current release, which I had already installed, has the same version as the GitHub repo (4.12.2).
Only after a while I realized that nothing was upgraded and I had to use --force-reinstall to do it.

I want to discuss if in the future, after some merged PRs, the version of the GitHub repo should be upgraded to a +1dev to not be equivalent to the latest release version.

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

        AltStyle によって変換されたページ (->オリジナル) /