Follow

There is a big change coming to pip in October -- a watershed moment, a minor revolution. It'll be a great foundation for making it easier to deal with packaging.

This is a thread where I'll share some of the stuff @`ThePyPA can build on that foundation.

· · Web · 1 · 5 · 10

github.com/pypa/pip/issues/53 A pip option to show what versions of packages are currently available. Maybe something like `pip install --dry-run`. This issue has been open since 2011. It's blocked on the new resolver.

Show thread

github.com/pypa/pip/issues/649 Dealing properly with the interaction of constraints & pinned requirements. Like, if

constraints.txt:
urllib3>1.23

requirements.txt:
urllib3==1.24.3

then pip should install urllib3==1.24.3, not 1.25.2.

Can't do this till pip's got the new resolver.

Show thread

github.com/pypa/pip/issues/455 Add a `pip upgrade-all` command. Instead of having to specify what pip should upgrade, or use a workaround add-on tool, it would be great to have a built-in tool to upgrade all packages in the environment. Wanted since 2011. Awaits the new resolver

Show thread

github.com/pypa/pip/issues/474 Add a "never" option for ``--upgrade-strategy``. Let the user set up a safeguard to avoid accidentally upgrading a particular package.

users want this too. The new resolver makes it a lot more possible.

Show thread

discuss.python.org/t/if-python Some folks are interested in splitting out some parts of the standard library into standalone packages, so that we can ship fixes quicker, and make the core smaller.

The new pip resolver would make this new state of affairs smoother.

Show thread

github.com/pypa/pipenv/issues? Use pipenv to handle packaging? It's got several open dependency resolution issues awaiting the resolver, or depending on pip-tools adapting to the new resolver.

Show thread

github.com/pypa/pip/issues/468 Warning the user when uninstalling, or upgrading, a package that other already-installed packages depend on. Waiting on the new pip resolver.

The list goes ON. The main issue github.com/pypa/pip/issues/988 has 172 comments, 62 participants, a zillion interlinks.

Show thread

What even is a dependency resolver and why is it important? And where did @`ThePSF and @`ThePyPA get the money to make this happen, after years of preparatory work? pyfound.blogspot.com/2019/12/m explains, and thanks @`mozilla and @`ChanZuckerberg .

(Midyear report pyfound.blogspot.com/2020/07/p )

Show thread

We applied for & got USD $407K in funding to do this work. Want to follow our lead? Read or watch my ten-minute @`PyOhio
talk "Apply for Grants To Fund Work". Sample funders, project help, case study, & tips.

changeset.nyc/resources/quick-

youtube.com/watch?v=EyhosW2Zea

[Fediverse-only note: the birdsite version of this toot is twitter.com/ChangesetLLC/statu and Twitter will show it to you directly, but if you're looking at the rest of the thread, this tweet is "not available". ?!]

Show thread

The new pip resolver will also unblock or even fix problems affecting hatch, Spyder, Django, cherrypy, cheroot, six, certbot, Mozilla.org, Canonical's DevOps tool Juju, and more -- some of the cases we know, we listed in github.com/psf/fundable-packag

Show thread
Sign in to participate in the conversation
Mastodon

Server run by the main developers of the project 🐘 It is not focused on any particular niche interest - everyone is welcome as long as you follow our code of conduct!