zpy VS rye

zpy – Zsh helpers for Python venvs, with uv or pip-tools

If your interactive shell is zsh, you could give my project zpy a try, particularly the function pipz that it provides, which is a lightweight pipx clone with great completions and good speed.

I can immediately see some things rye is doing differently, like keeping the venvs themselves free of pip and pip-tools. I wonder in your explorations if you've tried rtx for managing python installations, or my own zpy wrapper of pip-tools+venv (which can also replace pipx).

My patterns in this regard aren't exactly mainstream, as I use flit+pip-tools+zpy (the latter being my own Zsh interface for Python dependency and environment operations), but FWIW here's how I go about nested requirements.

For managing venvs and dependencies and apps, I use my own frontend to pip-tools + venv, zpy. And for running tasks which require an activated venv, I use nox.

If anyone's interested in a pipx clone with excellent tab completion, I would appreciate any feedback on pipz, a function of my zsh plugin for python environment and dependency management: zpy

https://github.com/andydecleyre/zpy

For concise and practical interactive usage of those tools, with excellent tab completion, I made the Zsh frontend zpy.

I also use my own Zsh wrapper functions with it, so for example: https://i.imgur.com/YX8bWy8.png

I'm a big fan of (and small contributor to) pip-tools, but both poetry and pipenv offer management of more stuff, which understandably appeals to folks seeking a simple comprehensible workflow.

Pip-tools is also a bit lower level, offering flexibility and compatibility which I relish, but also requiring more attention from the user to set things up as they wish.

If you or anyone else enjoying pip-tools is a Zsh user and interested in trying out my higher level functions to ease interactive use of pip-tools, venvs, and also isolated app installs (like pipx), I would love some feedback on zpy: https://github.com/AndydeCleyre/zpy

I'm very happy to answer any questions about it right here or as GitHub issues.

This is FAR from some big mainstream thing, but I use (and am happy to answer any questions about) my own Zsh frontend to venv+pip-tools+pip, zpy.

Yeah, the README said the following until January 2024 [1]:

> Rye is Armin's personal one-stop-shop for all his Python needs. [...] It is a wish of what Python was, with no guarantee to work for anyone else.

That text was removed only a few weeks before the announcement that Astral was taking stewardship of Rye.

[1]: https://github.com/astral-sh/rye/commit/f7c928898ae5f952fc2f...

I wrote about it a bit here: https://github.com/astral-sh/rye/discussions/1342

Isn't it Rye ? (https://rye.astral.sh)

I've been evaluating it lately and it has pretty much the same CLI commands as Poetry except it's faster and comes with complete Python interpreter management (which is to me the real killer feature as I don't really care about speed of dependency resolution, but I do care about the DX).

I haven't used uv but it looks like its trying to be a drop-in replacement for pip which would therefore lack everything that makes poetry great.

Rye on the other hand seems to be extremely poetry-like while being written in rust for speed: https://rye.astral.sh/

But personally, I can't justify switching my employer to experimental python dependency management over something as inconsequential as taking a minute to install dependencies so I'm sticking to poetry until Rye has some years of development behind it.

FYI, Rye is the name of a tool that's gaining popularity in the Python world. https://github.com/astral-sh/rye

One that that isn't clear is editor support -- I recently switched to poetry for a few repos at work because it took the pain out of editor setup for my team -- it works with intellij, vscode, and emacs (well, doom emacs made it pretty easy) -- anyone know how well this integrats with e.g. emacs?

A quick search turned up this unanswered question: https://github.com/astral-sh/rye/issues/888

On Rye: "This project was ultimately abandoned by its author in 2023 and given to Astral.sh in favor of supporting uv instead"

I don't think that's quite the right way to frame this. Handing Rye over to a company that could maintain it full time isn't the same thing as "abandoning" it - and the new maintainers are very active on that project: https://github.com/astral-sh/rye/commits/main/

Dependencies are managed with rye.