3 ms·
In the Python ecosystem there has been quite a bit of debate around workflow tools (Hatch, PDM, flit, Poetry etc.) I tried out Poetry starting in probably 2018
by zahlman 2y ago
In the Python ecosystem there has been quite a bit of debate around workflow tools (Hatch, PDM, flit, Poetry etc.) I tried out Poetry starting in probably 2018 or so and eventually realized how much I hated it: it was lagging behind on standards and the install/uninstall process was a moving target. But more than that, it... was an all-in-one tool, with its own definition of "all", almost all of which was irrelevant to me and which I was simply ignoring. I never ended up trying other options because I realized I would still have that same experience - although their various definitions of "all" are not identical.
I very much see the need in the Python ecosystem for a fully integrated user-level tool - something that sets up environments and allows people to use dependencies in their own one-off scripts. Pipx is almost there, if you build some wrappers around it to deal with the fact that it artificially refuses to "install" what it considers "libraries" (i.e. packages that don't define any explicit entry points). But it still is a bit rough around the edges, and more importantly is still based on Pip which has many faults. (I don't blame the design of `venv` for very much if anything, even if it's not quite how I would do things if we could start completely fresh; but it could use some nicer wrappers.)
But for development I've always thought it makes more sense to take a "Unix way" approach. Developers need the user tool for the basic mechanics of setting up packages, and then an actual toolchain built around that, with the chance to select individual tools according to their needs and preferences.