nix-cde VS zpy

This is what I'm using with gitlab: https://github.com/takeda/nix-cde/blob/master/contrib/gitlab...

I myself use https://github.com/takeda/nix-cde it just wraps other projects in an opinionated way and contains the boiler plate that I would normally use otherwise.

There's a project that does this with using Nix: https://github.com/takeda/nix-cde (this is a wrapper around https://github.com/nix-community/poetry2nix)

I personally use this: https://github.com/takeda/nix-cde it has the benefit of a reproducible build environment, but unfortunately anything involving Nix has a steep learning curve.

I use this myself: https://github.com/takeda/nix-cde

I don't use NixOS myself, but have Nix installed on my Mac, and it seems to provide all functionality of package or version managers I needed.

I think though it is more complex because it is a programming language that provides this functionality instead of purpose build tool like asdf.

For my needs I created a framework for development: https://github.com/takeda/nix-cde to avoid cruft of including the same things over and over in my projects.

Not an OP, but I became a big fan of using poetry for managing dependencies. For managing python version I started using Nix package manager. It allows to describe all dependencies via code, but with time that code became a boilerplate, so I created this: https://github.com/takeda/nix-cde

It works very well for me so far.

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.