New PyPI launched, legacy PyPI shutting down April 30
Starting today, the canonical Python Package Index is at https://pypi.org and uses the new Warehouse codebase.
We announced the https://pypi.org beta on March 26 and your feedback and test usage have helped us get it production-ready.
Monday April 16 (2018-04-16): We launched the new PyPI, redirecting browser traffic and API calls (including "pip install") from pypi.python.org to the new site. The old codebase is still available at https://legacy.pypi.org for now.
Monday April 30 (2018-04-30): We plan to shut down legacy PyPI https://legacy.pypi.org . The address pypi.python.org will continue to redirect to Warehouse.
For more details, see our roadmap: https://wiki.python.org/psf/WarehouseRoadmap
If your site/service links to or uses pypi.python.org, you should start using pypi.org instead: https://warehouse.readthedocs.io/api-reference/integration-guide/#migrating-to-the-new-pypi
Thank you.
-Sumana Harihareswara on behalf of the PyPI Team
Monday, April 16, 2018
Saturday, April 14, 2018
Python 2.7.15 release candidate 1 is now available
Python 2.7.15 release candidate 1 is now available for download. Please test with your applications and libraries and report any bugs. A final 2.7.15 release is expected at the end of April.
Pip 10 has been released
On behalf of the PyPA, I am pleased to announce that pip 10.0 has just been released. This release has been the culmination of many months of work by the community.
To install pip 10.0, you can run
python -m pip install --upgrade pip
or use get-pip, as described in https://pip.pypa.io/en/latest/installing. If you are using a version of pip supplied by your distribution vendor, vendor-supplied upgrades will be available in due course (or you can use pip 10 in a virtual environment).
(One minor issue with using get-pip on Windows - when you download get-pip.py, rename it to something that doesn't include "pip" in the name, such as "gp.py", as the standard name triggers a check in pip that aborts the run - this is being tracked in https://github.com/pypa/pip/issues/5219).
Highlights of the new release:
internals has now taken place. Unless you are the author of code that
imports the pip module (or a user of such code), this change will not
affect you. If you are affected, please report the issue to the author of the
offending code (refer them to
https://mail.python.org/pipermail/distutils-sig/2017-October/031642.html
for the details of the announcement).
Thanks to everyone who put so much effort into the new release. Many
of the contributions came from community members, whether in the form
of code, participation in design discussions, or bug reports. The pip
development team is extremely grateful to everyone in the community
for their contributions.
Thanks,
Paul
To install pip 10.0, you can run
python -m pip install --upgrade pip
or use get-pip, as described in https://pip.pypa.io/en/latest/installing. If you are using a version of pip supplied by your distribution vendor, vendor-supplied upgrades will be available in due course (or you can use pip 10 in a virtual environment).
(One minor issue with using get-pip on Windows - when you download get-pip.py, rename it to something that doesn't include "pip" in the name, such as "gp.py", as the standard name triggers a check in pip that aborts the run - this is being tracked in https://github.com/pypa/pip/issues/5219).
Highlights of the new release:
- Python 2.6 is no longer supported - if you need pip on Python 2.6, you should stay on pip 9, which is the last version to support Python 2.6.
- Support for PEP 518, which allows projects to specify what packages they require in order to build from source. (PEP 518 support is currently limited, with full support coming in future versions - see the documentation for details).
- Significant improvements in Unicode handling for non-ASCII locales on Windows.
- A new "pip config" command.
- The default upgrade strategy has become "only-if-needed"
- Many bug fixes and minor improvements.
internals has now taken place. Unless you are the author of code that
imports the pip module (or a user of such code), this change will not
affect you. If you are affected, please report the issue to the author of the
offending code (refer them to
https://mail.python.org/pipermail/distutils-sig/2017-October/031642.html
for the details of the announcement).
Thanks to everyone who put so much effort into the new release. Many
of the contributions came from community members, whether in the form
of code, participation in design discussions, or bug reports. The pip
development team is extremely grateful to everyone in the community
for their contributions.
Thanks,
Paul
Subscribe to:
Posts (Atom)