On behalf of the Python Packaging Authority <https://pypa.io/>, I am pleased to 
announce that we have just 
released pip 20.3, a new version of pip. You can install it by running python 
-m pip install --upgrade pip.


(Below is basically a copy of the announcement we made on our developers' 
forum/mailing list 
<https://discuss.python.org/t/announcement-pip-20-3-release/5948>. If you're 
spreading the word about this widely, the blog post 
<https://pyfound.blogspot.com/2020/11/pip-20-3-new-resolver.html> is probably a 
better choice to link to.)
This is an important and disruptive release – we explained why in a blog post 
last year <https://pyfound.blogspot.com/2019/12/moss-czi-support-pip.html>. We 
even made a video about it <https://www.youtube.com/watch?v=B4GQCBBsuNU>.


Highlights


 * *DISRUPTION*: Switch to the new dependency resolver by default. Watch out 
for changes in handling editable installs, constraints files, and more: 
https://pip.pypa.io/en/latest/user_guide/#changes-to-the-pip-dependency-resolver-in-20-3-2020


 * *DEPRECATION*: Deprecate support for Python 3.5 (to be removed in pip 21.0)


 * *DEPRECATION*: pip freeze will stop filtering the pip,
 setuptools, distribute and wheel packages from pip freeze output in a 
future version. To keep the previous behavior, users should use the new 
--exclude option.


 * Substantial improvements in new resolver for performance, output and 
error messages, avoiding infinite loops, and support for constraints 
files.


 * Support for PEP 600: Future ‘manylinux’ Platform Tags for Portable Linux 
Built Distributions. 


 * Documentation improvements: Resolver migration guide, quickstart guide, and 
new documentation theme.


 * Add support for MacOS Big Sur compatibility tags.


The new resolver is now *on by default*. It is significantly 
stricter and more consistent when it receives incompatible instructions,
 and reduces support for certain kinds of constraints files, so some 
workarounds and workflows may break. Please see our guide on how to test and 
migrate, and how to report issues  
<https://pip.pypa.io/en/latest/user_guide/#changes-to-the-pip-dependency-resolver-in-20-3-2020>.
 You can use the deprecated (old) resolver, using the flag 
--use-deprecated=legacy-resolver, until we remove it in the pip 21.0 release in 
January 2021.


You can find more details (including deprecations and removals) in the 
changelog <https://pip.pypa.io/en/stable/news/>.


User experience


Command-line output for this version of pip, and documentation to 
help with errors, is significantly better, because you worked with our 
experts to test and improve it. Contribute to our user experience work: sign up 
to become a member of the UX Studies group <https://bit.ly/pip-ux-studies> 
(after you join, we’ll notify you about future UX surveys and interviews).


What to expect in 21.0


We aim to release pip 21.0 in January 2021, per our usual release cadence 
<https://pip.pypa.io/en/latest/development/release-process/#release-cadence>. 
You can expect:


 * Removal of Python 2.7 
<https://pip.pypa.io/en/latest/development/release-process/#python-2-support> 
and 3.5 support
 * Further improvements in the new resolver
 * Removal of legacy resolver support
Thanks


As with all pip releases, a significant amount of the work was 
contributed by pip’s user community. Huge thanks to all who have 
contributed, whether through code, documentation, issue reports and/or 
discussion. Your help keeps pip improving, and is hugely appreciated.


Specific thanks go to Mozilla (through its Mozilla Open Source Support 
<https://www.mozilla.org/en-US/moss/> Awards) and to the Chan Zuckerberg 
Initiative <https://chanzuckerberg.com/eoss/> DAF, an advised fund of Silicon 
Valley Community Foundation, for their 
funding that enabled substantial work on the new resolver.


That funding went to Simply Secure <https://simplysecure.org/> (specifically 
Georgia Bullen, Bernard Tyers, Nicole Harris, Ngọc Triệu, and Karissa 
McKelvey), Changeset Consulting <https://changeset.nyc/> (Sumana 
Harihareswara), Atos  <https://www.atos.net/> (Paul F. Moore), Tzu-ping Chung 
<https://uranusjr.com/>, Pradyun Gedam <https://pradyunsg.me/>, and Ilan 
Schnell. Thanks also to Ernest W. Durbin III at the Python Software Foundation 
for liaising with the project.


-Sumana Harihareswara, pip project manager
------------------------------------------
This list is for the purpose of general discussion about The Carpentries 
including community activities, upcoming events, and announcements.  Some other 
lists you may also be interested in include discuss-hpc, discuss-r, and  our 
local groups. Visit https://carpentries.topicbox.com/groups/ to learn more. All 
activity on this and other Carpentries spaces should abide by The Carpentries 
Code of Conduct found here: 
https://docs.carpentries.org/topic_folders/policies/code-of-conduct.html

The Carpentries: discuss
Permalink: 
https://carpentries.topicbox.com/groups/discuss/T4bf0a9d08b83415f-Mda03703180ea4a4d8e6d4f6c
Delivery options: https://carpentries.topicbox.com/groups/discuss/subscription

Reply via email to