Add build number identifiers to version numbers reported by pip

[TheFriendlyCoder]

• Pip version: 10.0.0b2
• Python version: 3.6
• Operating system: Mac OSX

Description:

In situations where pip presents version information about packages, like when running pip freeze, pip list and even in the error output produced by pip install, the names and version numbers of the packages are presented but the build numbers are excluded. In order to more accurately reflect the content related to these packages these display messages should be updated to include the build numbers, when available, of the packages as well

What I've run:

pip list

expected output:

Package             Version           Build
------------------------------------
MyPackage         1.0.0               12345

actual output:

Package             Version
------------------------
MyPackage         1.0.0

[TheFriendlyCoder]

This proposed improvement relates to PR #4299

[pradyunsg]

@TheFriendlyCoder Thanks for filing this issue! :)

This sounds reasonable to me.

I think including the build number in the version column in some way, is an idea worth exploring.

[pradyunsg]

I've labelled this issue as an "deferred PR".

This label is essentially for indicating that further discussion related to this issue should be deferred until someone comes around to make a PR. This does not mean that the said PR would be accepted - it has not been determined whether this is a useful change to pip and that decision has been deferred until the PR is made.

[chrahunt]

The build number is only expected to be in wheel filenames and isn't persisted anywhere. I don't think we'd want to add it to the installed package metadata without a PEP update (at which time it would likely be the responsibility of the package to include the field and pip could display it).

[pfmoore]

I don't think we'd want to add it to the installed package metadata without a PEP update

Agreed.

[devinrsmith]

@chrahunt - at least according to this https://peps.python.org/pep-0427/#file-contents, the build number makes it into dist-info/WHEEL.

[uranusjr]

I changed the state, PR is welcomed. This can likely be handled similarly to Location (i.e. add a column right after Version if any of the listed packages has a build number). The content of WHEEL is accessible with the metadata interface.

[WoodyWu0310]

I also want it. In conda list, it shows internal build number. Like

#Name                    Version                   Build  Channel
bzip2                     1.0.8                he774522_0

My team using "version number + internal build number" to identify a 3rd site package, In order to avoid "the version number is same , but codes are different"
Buti in pip list, it only shows

Package         Version
--------------- -------
click           8.1.3