2 ms·
Hi HN, This is the second post in my series, which I wrapped up quite late last night and am finally getting around to submitting here, not-as-late tonight. In
by zahlman 2y ago
Hi HN,
This is the second post in my series, which I wrapped up quite late last night and am finally getting around to submitting here, not-as-late tonight. In this one I highlight some of the benefits of using Pipx to install Python applications - relevant both for end users and for developers. I also discuss some of the limits that you'll run into with it (especially as a developer), and show some neat ways to work around issues and get more out of your Pipx installation.
In particular, a few setup steps and wrapper scripts allow you to reuse Pipx's vendored copy of Pip for any virtual environment on your system (and create new virtual environments faster, by not bootstrapping a copy of Pip into them), and to get raw access to the virtual environments that Pipx creates - allowing you to explore and debug installed code, and treat Pipx like a primitive environment manager.
From my point of view, the advice I offer here is a stopgap - one of the tools I'm developing, Paper, is intended to replace both Pip and Pipx (although the intended scope is still nowhere near "complete workflow tool"). But hopefully you find it useful right away.
Later this month I'm planning a broader piece about my experience with Linux, and especially my experience of using Python on Linux, and the scripts I show here will be some useful background for that.
My next planned post is about a long-standing (I mean over a decade) bug in Pip which I consider both surprising and embarrassing (and arguably an important security issue).
- ggm 2y agoIf you use homebrew on OSX you are recommended to use pipx by pip3, under the homebrew model (if you install python as a brew) I didn't for ages. Then, I did and I found it worked, and did not whine about breaking pip based brew based package management so I am happy(ier)
- zahlman 2y agoInteresting. I probably should come back to this piece later and expand it to talk more about why you'd want to solve the problems that Pipx solves (i.e. the externally managed environment stuff - I think I only included a link for context).