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

Ignore pre-release versions when prompting for upgrade #5470

Conversation

TheJokersThief
Copy link

This is a PR to solve #5175.

The possible candidates for updating are filtered to remove any versions that contain a pre-release.

I've also updated the unit test to properly reproduce and test for the error. The old values for the versions didn't trigger it but the new versions committed will.

@pradyunsg
Copy link
Member

pradyunsg commented Jun 4, 2018

Thanks for the PR on this @TheJokersThief! :)

@pypa/pip-committers I was wondering if pip should show a message when there's pre-release versions available; asking the user to test them if they can.

If we go this way, one case that comes to mind is what should happen when someone's on 18.0, there's an 18.1 and 18.2b1 available? 2 messages? Only one message suggesting the normal upgrade?

I'd say 2 messages, as long as they're unambiguously worded.

@pradyunsg pradyunsg added type: enhancement Improvements to functionality S: needs triage Issues/PRs that need to be triaged and removed S: needs triage Issues/PRs that need to be triaged labels Jun 4, 2018
@pradyunsg
Copy link
Member

@pypa/pip-committers Ping?

@pfmoore
Copy link
Member

pfmoore commented Jan 8, 2019

I was wondering if pip should show a message when there's pre-release versions available; asking the user to test them if they can.

Meh. We have prereleases so infrequently, it's not a big deal. And the lack of experience with having them means any decisions we make about what's the best way of designing it are likely just guesswork.

So basically I don't think it's worth it.

As to this PR, I don't really mind either way. It's just as easy to ignore the upgrade message if it's offering a pre-release version.

@xavfernandez
Copy link
Member

I'd be in favor of merging this and not prompting the user to use a prerelease.

@BrownTruck
Copy link
Contributor

Hello!

I am an automated bot and I have noticed that this pull request is not currently able to be merged. If you are able to either merge the master branch into this pull request or rebase this pull request against master then it will be eligible for code review and hopefully merging!

@BrownTruck BrownTruck added the needs rebase or merge PR has conflicts with current master label Apr 17, 2019
@cjerdonek
Copy link
Member

This was superseded by PR #5971 (now merged). Thank you for your contribution to addressing this issue!

@cjerdonek cjerdonek closed this Apr 17, 2019
@lock
Copy link

lock bot commented May 28, 2019

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot added the auto-locked Outdated issues that have been locked by automation label May 28, 2019
@lock lock bot locked as resolved and limited conversation to collaborators May 28, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
auto-locked Outdated issues that have been locked by automation needs rebase or merge PR has conflicts with current master type: enhancement Improvements to functionality
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants