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.

Sign up for GitHub

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

Jump to bottom

Display pre-release version hint in package version output of "pip search" (and others) #5169

Closed
novoid opened this issue Apr 5, 2018 · 1 comment · Fixed by #5921
Closed

Display pre-release version hint in package version output of "pip search" (and others) #5169

novoid opened this issue Apr 5, 2018 · 1 comment · Fixed by #5921
Labels
auto-locked Outdated issues that have been locked by automation good first issue A good item for first time contributors to work on type: enhancement Improvements to functionality

Comments

@novoid
Copy link

novoid commented Apr 5, 2018 •
edited
Loading

  • Pip version: pip 9.0.3 from c:\python36\lib\site-packages (python 3.6)
  • Python version: Python 3.6.2
  • Operating system: Windows 10

Description:

In #5168 I learned that version numbers like "2018.04.04a" are interpreted as pre-release versions. Therefore I could not install them without adding the parameter --pre.

However, this is implicit knowledge the user must have about interpretations of version numbers and related pip behavior in order to understand the behavior of pip. Otherwise, the user is irritated, just like I was until a couple of minutes ago.

Current situation where 2018.04.04a is not installable when --pre is not given:

C:\Users\karl.voit>pip search filetags
filetags (2018.04.04a)  - Management of simple tags within file names
  INSTALLED: 2018.3.19
  LATEST:    2018.04.04a

C:\Users\karl.voit>

Shouldn't there at least be a hint such as following suggestion?

C:\Users\karl.voit>pip search filetags
filetags (2018.04.04a)  - Management of simple tags within file names
  INSTALLED: 2018.3.19
  LATEST:    2018.04.04a (pre-release; install with "pip install --pre")

C:\Users\karl.voit>

Maybe this applies for multiple stdout messages.

What I've run:

See #5168 to give you some background.
@pradyunsg pradyunsg added the type: enhancement Improvements to functionality label Apr 5, 2018
@pradyunsg pradyunsg added this to the Improve User Experience milestone Apr 5, 2018
@pradyunsg pradyunsg removed this from the Improve User Experience milestone May 13, 2018
@pradyunsg pradyunsg added the good first issue A good item for first time contributors to work on label May 13, 2018
@demophoon demophoon mentioned this issue May 15, 2018
Closed
demophoon added a commit to demophoon/pip that referenced this issue Sep 25, 2018
@demophoon
Add hint when displaying pre-released package if an update exists
b67a7c9 
Before this commit when querying for an installed package using pip if
the package that was returned contained a pre-released version of the
package it was not intuitive that the pre-released version of the
package could not be directly upgraded to without the `--pre` flag.

This commit shows additional information on how to upgrade to
pre-released versions of a package if one is found in the search.

Fixes pypa#5169.
@lkollar lkollar mentioned this issue Oct 26, 2018
Merged
@S-B1
Copy link

S-B1 commented Oct 28, 2018

An approved pull request exists for this.

@lock lock bot added the auto-locked Outdated issues that have been locked by automation label Jun 26, 2019
@lock lock bot locked as resolved and limited conversation to collaborators Jun 26, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
auto-locked Outdated issues that have been locked by automation good first issue A good item for first time contributors to work on type: enhancement Improvements to functionality
Projects
None yet
Milestone
No milestone
3 participants
@novoid @pradyunsg @S-B1