A 3.7 update: Python 3.7.0b5 is now the final beta preview of Python 3.7, the next feature release of Python. 3.7.0b4 was intended to be the final beta but, due to some unexpected compatibility issues discovered during beta testing of third-party packages, we decided to revert some changes in how Python's 3.7 Abstract Syntax Tree parser deals with docstrings; 3.7.0b5 now behaves like 3.6.x and previous releases (refer to the 3.7.0b5 changelog for more information). If your code makes use of the ast module, you are strongly encouraged to test (or retest) that code with 3.7.0b5, especially if you previously made changes to work with earlier preview versons of 3.7.0. As always, please report issues found to bugs.python.org as soon as possible. Please keep in mind that this is a preview release and its use is not recommended for production environments. Attention macOS users: there is now a new installer variant for macOS 10.9+ that includes a built-in version of Tcl/Tk 8.6. This variant is expected to become the default version when 3.7.0 releases. Check it out!
The next (and final, we hope!) preview release will be the release candidate which is now planned for 2018-06-11 followed by the official release of 3.7.0, now planned for 2018-06-27. You can find Python 3.7.0b5 and more information here:
Thursday, May 31, 2018
Wednesday, May 2, 2018
Python 3.7.0b4, final 3.7 beta, now available for testing
Python 3.7.0b4 is the final beta preview of Python 3.7, the next feature release of Python. Beta releases are intended to give you the opportunity to test new features and bug fixes and to prepare your projects to support the new feature release. We strongly encourage you to test your projects with 3.7 during the beta phase and report issues found to bugs.python.org as soon as possible. While the release is feature complete entering the beta phase, it is possible that features may be modified or, in rare cases, deleted up until the start of the release candidate phase. Please keep in mind that this is a preview release and its use is not recommended for production environments. Attention macOS users: there is now a new installer variant for macOS 10.9+ that includes a built-in version of Tcl/Tk 8.6. This variant is expected to become the default version when 3.7.0 releases. Check it out!
The next preview release will be the release candidate and is planned for 2018-05-21 followed by the official release of 3.7.0, planned for 2018-06-15. You can find Python 3.7.0b4 and more information here:
The next preview release will be the release candidate and is planned for 2018-05-21 followed by the official release of 3.7.0, planned for 2018-06-15. You can find Python 3.7.0b4 and more information here:
Labels:
releases
Tuesday, May 1, 2018
Python 2.7.15 released
The bugfix release Python 2.7.15 is now available for download.
Monday, April 16, 2018
New PyPI launched, legacy PyPI shutting down April 30
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
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
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
Saturday, March 31, 2018
Beta release of pip version 10
On behalf of the PyPA, I am pleased to announce that a beta release
10.0.0b1 of pip has just been released for testing by the community.
We're planning on a final release in 2 weeks' time, over the weekend
of 14/15 April.
To install pip 10.0.0.b1, you can run
python -m pip install --upgrade --pre pip
(obviously, you should not do this in a production environment!)
We would be grateful for all testing that users could do, to ensure
that when pip 10 is released it's as solid as we can make it.
Highlights of the new release:
In addition, the previously announced reorganisation of pip's
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, please report the issue to the author of the
affected code (refer them to
https://mail.python.org/
for the details of the announcement).
Please note that there is a minor issue with the NEWS file for this
release - the new features in 10.0.0b1 are reported as being for
"9.0.3 (2018-03-31)".
If you discover any bugs while testing the new release, please report
them at https://github.com/pypa/pip/
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
10.0.0b1 of pip has just been released for testing by the community.
We're planning on a final release in 2 weeks' time, over the weekend
of 14/15 April.
To install pip 10.0.0.b1, you can run
python -m pip install --upgrade --pre pip
(obviously, you should not do this in a production environment!)
We would be grateful for all testing that users could do, to ensure
that when pip 10 is released it's as solid as we can make it.
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.
In addition, the previously announced reorganisation of pip's
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, please report the issue to the author of the
affected code (refer them to
https://mail.python.org/
for the details of the announcement).
Please note that there is a minor issue with the NEWS file for this
release - the new features in 10.0.0b1 are reported as being for
"9.0.3 (2018-03-31)".
If you discover any bugs while testing the new release, please report
them at https://github.com/pypa/pip/
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)