The Python package installer https://pip.pypa.io/
Go to file
Igor Kuzmitshov 2bdc93dd7b Fix the latest version number in search results
When listing found packages, `print_results()` uses the last version in
the versions list of a package, but that version is not necessarily the
latest. For example, `SearchCommand.search()` may return the following
(tested with JFrog Artifactory PyPI repo):

    pypi_hits = command.search(args, options)

    [{'_pypi_ordering': 1,
      'name': 'testlib',
      'summary': 'Test library.',
      'version': '1.0.5'},
     {'_pypi_ordering': 0,
      'name': 'testlib',
      'summary': 'Test library.',
      'version': '1.0.3'}]

`pip.commands.search.transform_hits()` preserves the order of versions:

    hits = pip.commands.search.transform_hits(pypi_hits)

    [{'name': 'testlib',
      'summary': 'Test library.',
      'versions': ['1.0.5', '1.0.3']}]

`pip.commands.search.print_results()` uses the last version in the list:

    pip.commands.search.print_results(hits)

    testlib (1.0.3)  - Test library.

Expected result:

    testlib (1.0.5)  - Test library.

`print_results()` uses `highest_version()` already to compare the
installed version with the latest found version (for installed
packages). Same function is used in this fix to show the latest
versions of all found packages.
2017-01-09 23:43:29 +00:00
.github Create ISSUE_TEMPLATE.md 2016-02-27 00:35:56 +11:00
.travis Change "tmpdir" fixture to work with latest pytest 2016-07-21 21:50:34 -03:00
contrib Move get-pip.py to its own repository 2016-01-20 08:53:45 -05:00
docs Add a note to the docs about 2.6/get-pip.py (#4095) 2016-11-06 18:48:35 -05:00
pip Fix the latest version number in search results 2017-01-09 23:43:29 +00:00
tasks Automatic vendoring (#4093) 2016-11-06 17:34:10 -05:00
tests Fix the latest version number in search results 2017-01-09 23:43:29 +00:00
.coveragerc Show coverage information for tests 2014-06-30 20:59:32 -04:00
.gitignore ignore more vestiges of the test suite 2016-11-21 10:07:33 +01:00
.landscape.yml Add landscape.io configuration file 2016-01-02 20:55:18 +01:00
.mailmap Update the AUTHORS.txt file 2015-04-07 00:37:41 -04:00
.travis.yml Switch to 3.6.0 final as our latest 3.x release (#4202) 2016-12-24 12:38:01 -08:00
AUTHORS.txt Update AUTHORS 2016-11-06 13:45:48 -05:00
CHANGES.txt Failing exit status when no requirements specified (#4210) 2017-01-06 23:21:46 +01:00
LICENSE.txt Updated copyright to 2016 2016-01-01 01:58:28 +00:00
MANIFEST.in Ignore .github files from the manifest 2016-02-27 18:16:10 +11:00
README.rst README.rst add link to AppVeyor build status 2016-10-19 13:32:56 +03:00
appveyor.yml Don't use toxenv on appveyor, as it has no way of coping with 64-bit Python versions 2015-12-02 14:28:37 +00:00
dev-requirements.txt Use pytest-catchlog instead of pytest-capturelog 2016-07-28 21:35:52 -03:00
setup.cfg Use the new wheel config section 2015-10-02 01:26:59 +01:00
setup.py Specify the supported python version via python_requires (#3860) 2016-07-21 12:49:53 -04:00
tox.ini Fix travis and tox configurations for 3.6 and 3.7 2016-10-15 23:43:58 +02:00

README.rst

pip
===

The `PyPA recommended
<https://packaging.python.org/en/latest/current/>`_
tool for installing Python packages.

* `Installation <https://pip.pypa.io/en/stable/installing.html>`_
* `Documentation <https://pip.pypa.io/>`_
* `Changelog <https://pip.pypa.io/en/stable/news.html>`_
* `Github Page <https://github.com/pypa/pip>`_
* `Issue Tracking <https://github.com/pypa/pip/issues>`_
* `User mailing list <http://groups.google.com/group/python-virtualenv>`_
* `Dev mailing list <http://groups.google.com/group/pypa-dev>`_
* User IRC: #pypa on Freenode.
* Dev IRC: #pypa-dev on Freenode.


.. image:: https://img.shields.io/pypi/v/pip.svg
   :target: https://pypi.python.org/pypi/pip

.. image:: https://img.shields.io/travis/pypa/pip/master.svg
   :target: http://travis-ci.org/pypa/pip

.. image:: https://img.shields.io/appveyor/ci/pypa/pip.svg
   :target: https://ci.appveyor.com/project/pypa/pip/history

.. image:: https://readthedocs.org/projects/pip/badge/?version=stable
   :target: https://pip.pypa.io/en/stable

Code of Conduct
---------------

Everyone interacting in the pip project's codebases, issue trackers, chat
rooms, and mailing lists is expected to follow the `PyPA Code of Conduct`_.

.. _PyPA Code of Conduct: https://www.pypa.io/en/latest/code-of-conduct/