Distutils-SIG December 2018

distutils-sig@python.org

17 participants
12 discussions

upcoming work to facilitate PyPA communications/roadmaps

by Sumana Harihareswara

It's been eight months since the release of Warehouse[0] and the sunsetting of legacy PyPI[1]. Following up from our meeting at PyCon in May[2], Changeset Consulting is back on board for another round of project management to facilitate next steps! For the next 3-6 months this work will be spearheaded by myself (Sumana) assisted by Jenny Ryan (https://jennyryan.net ). The goal over these upcoming months is to create, steward and facilitate internal and public-facing communications to aid the folks within PyPA. What this means is that we'll be focused on the following: * Facilitating regular meetings of and for maintainers and contributors; * Stewarding communications with various PyPA stakeholders, including funders and users; * Organizing, labelling, prioritizing, and responding to GitHub issues; * Coordinating public communications, such as announcements, sprints, and calls for participation; * Maintaining and improving documentation, meeting notes and development roadmaps for PyPA projects. Feedback from and participation by the Python packaging developer community is obviously part and parcel of this project, so you may see some new "here's what I think is up with this issue, is that right?" questions on old unresolved discussions. And we'll be asking questions on this & other lists and on GitHub and in IRC to collect ideas, concerns, and other productive input regarding the tools roadmaps. You'll be seeing more details in mid-January to properly kick off this next chapter of levelling up PyPI and the PyPA -- just wanted to give y'all a heads-up. But of course, if you were already planning on using the next few weeks to do issue triage and roadmap-writing and PyCon planning, please don't wait for us -- that'll make this work all the easier. Thanks, Sumana Harihareswara [0] https://blog.python.org/2018/04/new-pypi-launched-legacy-pypi-shutting.html [1] https://mail.python.org/archives/list/distutils-sig@python.org/thread/YREMU… [2] https://mail.python.org/archives/list/distutils-sig@python.org/thread/CCOV6… -- Sumana Harihareswara Changeset Consulting https://changeset.nyc

2 years, 9 months

older pypi packages

by Robin Becker

I recently had to rebuild a server and find that pip 18.1 is apparently unable to install at least some older packages eg > $ bin/pip install fcrypt > Collecting fcrypt > Could not find a version that satisfies the requirement fcrypt (from versions: ) > No matching distribution found for fcrypt the version I needed is in fact the last released 1.3.1 (in 2004) and it was installed by an earlier pip. I tried being more explicit > $ bin/pip install fcrypt==1.3.1 > Collecting fcrypt==1.3.1 > Could not find a version that satisfies the requirement fcrypt==1.3.1 (from versions: ) > No matching distribution found for fcrypt==1.3.1 I assume that latest pip needs information from the package / pypi data that is not available. Luckily installing from a pypi download works. Is there any legacy mode in pip? It seems wrong to cause these older packages to become unusable. -- Robin Becker

2 years, 9 months

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

1999

1998

Distutils-SIG December 2018