Mailman 3 August 2020 - PSF-Community

Fwd: [pypi-announce] upgrade to pip 20.2 -- plus changes coming in 20.3
by Sumana Harihareswara Sept. 29, 2020

Sept. 29, 2020

A new release of pip is out. Please see below, upgrade, and let us know if you or your users start to have trouble. In particular, we need your feedback on the beta of the new dependency resolver, because we want to make it the default in the October release. Please report bugs using this survey: https://tools.simplysecure.org/survey/index.php?r=survey/index&sid=989272&l… . And please **spread the word** by pointing to this blog post: https://blog.python.org/2020/07/upgrade-pip-20-2-changes-20-3.html -- spread the word on Hacker News, Reddit, Twitter, Facebook, Dev.to, Telegram, relevant Stack Overflow answers, your favorite Slacks and Discords, etc. Most of the people this will affect do not keep up with Python-specific developer news. Help them get the heads-up before October, and help us get their bug reports. best, Sumana Harihareswara, pip project manager -------- Forwarded Message -------- Subject: [pypi-announce] upgrade to pip 20.2 -- plus changes coming in 20.3 Date: Thu, 30 Jul 2020 11:24:58 -0400 From: Sumana Harihareswara <sh(a)changeset.nyc> Reply-To: distutils-sig(a)python.org Organization: Changeset Consulting To: pypi-announce(a)python.org On behalf of the Python Packaging Authority, I am pleased to announce the release of pip 20.2. Please upgrade for speed improvements, bug fixes, and better logging. You can install it by running python -m pip install --upgrade pip. We make major releases each quarter, so this is the first new release since 20.1 in April. NOTICE: This release includes the beta of the next-generation dependency resolver. 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 test it with the `--use-feature=2020-resolver` flag. 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-res…>. The new dependency resolver is *off by default* because it is *not yet ready for everyday use*. For release highlights and thank-yous, please see <https://blog.python.org/2020/07/upgrade-pip-20-2-changes-20-3.html> . The full changelog is at <https://pip.pypa.io/en/stable/news/>. Future: We plan to make pip's next quarterly release, 20.3, in October 2020. We are preparing to change the default dependency resolution behavior and make the new resolver the default in pip 20.3. -- Sumana Harihareswara project manager for pip, on contract with Python Software Foundation Changeset Consulting, https://changeset.nyc _______________________________________________ pypi-announce mailing list -- pypi-announce(a)python.org To unsubscribe send an email to pypi-announce-leave(a)python.org https://mail.python.org/mailman3/lists/pypi-announce.python.org/

2 2

Invitation to PSF Trademarks Working Group
by David Mertz Aug. 22, 2020

Aug. 22, 2020

Hi Community, Through the inevitable attribution process of volunteer groups, our very important Trademarks Working Group has much less participation than we would like to have. So this is an invitation for community members to help out by joining the committee. Basically, your responsibilities involve reading the Trademark Usage Policy, maybe skimming the old archive to get a sense of our concerns and standards, and responding to maybe 6-7 emails a month to help judge whether we can authorize a given trademark usage. Let me know to volunteer. We'd like a few people who can reasonably commit to keep an eye on it for a reasonably long continuous period of time (say the next year). But it's a low-work ongoing commitment, and is really central to the PSF's mission. Yours, David Mertz Co-chair Python Software Foundation Trademarks Committee -- Keeping medicines from the bloodstreams of the sick; food from the bellies of the hungry; books from the hands of the uneducated; technology from the underdeveloped; and putting advocates of freedom in prisons. Intellectual property is to the 21st century what the slave trade was to the 16th.

5 6

Re: [PSF-Community] Invitation to PSF Trademarks Working Group
by Gajendra Deshpande Aug. 22, 2020

Aug. 22, 2020

Dear David, I would like to volunteer for the PSF Trademarks Working Group. Kindly consider me in. Thanks and Regards Gajendra C. Deshpande Assistant Professor, CSE(a)KLS.GIT Belgaum - 590008 Karnataka, INDIA Blog: http://gajendramoksha.wordpress.com Website: http://sites.google.com/a/git.edu/gcd Facebook: https://www.facebook.com/gcdeshpande [http://csta.acm.org/Membership/sub/badge.jpg]

1 0

Re: [PSF-Community] PSF-Community Digest, Vol 59, Issue 1
by Adekanye Tomi Aug. 21, 2020

Aug. 21, 2020

Hi David, I would love to volunteer. Thanks On Fri, Aug 21, 2020, 5:01 PM <psf-community-request(a)python.org> wrote: > Send PSF-Community mailing list submissions to > psf-community(a)python.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://mail.python.org/mailman/listinfo/psf-community > or, via email, send a message with subject or body 'help' to > psf-community-request(a)python.org > > You can reach the person managing the list at > psf-community-owner(a)python.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of PSF-Community digest..." > > > Today's Topics: > > 1. Invitation to PSF Trademarks Working Group (David Mertz) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Fri, 21 Aug 2020 10:52:12 -0400 > From: David Mertz <mertz(a)gnosis.cx> > To: PSF Community <psf-community(a)python.org> > Subject: [PSF-Community] Invitation to PSF Trademarks Working Group > Message-ID: > <CAEbHw4YfPTmWu7= > 4BHhNsFGeHUPO9PRgeX+ecZ+K1QEWvCy3Jg(a)mail.gmail.com> > Content-Type: text/plain; charset="utf-8" > > Hi Community, > > Through the inevitable attribution process of volunteer groups, our very > important Trademarks Working Group has much less participation than we > would like to have. > > So this is an invitation for community members to help out by joining the > committee. Basically, your responsibilities involve reading the Trademark > Usage Policy, maybe skimming the old archive to get a sense of our concerns > and standards, and responding to maybe 6-7 emails a month to help judge > whether we can authorize a given trademark usage. > > Let me know to volunteer. We'd like a few people who can reasonably commit > to keep an eye on it for a reasonably long continuous period of time (say > the next year). But it's a low-work ongoing commitment, and is really > central to the PSF's mission. > > Yours, David Mertz > Co-chair Python Software Foundation Trademarks Committee > > -- > Keeping medicines from the bloodstreams of the sick; food > from the bellies of the hungry; books from the hands of the > uneducated; technology from the underdeveloped; and putting > advocates of freedom in prisons. Intellectual property is > to the 21st century what the slave trade was to the 16th. >

1 0