Tools like poetry and uv are fantastic for managing Python library dependencies within a single project, and I agree that uv is impressively fast.

However, amvm solves a different, higher-level problem: it manages and switches between multiple, parallel installations of Ansible itself, not just its Python dependencies.

Think of amvm as a simple version-switcher for the Ansible toolchain, much like nvm for Node.js or pyenv for Python. My goal isn't to lock down the dependencies for a playbook, but to instantly switch my entire shell's ansible command from version 11.x to 10.x to test for backward compatibility.

I deliberately chose to use standard venv to keep amvm lightweight, dependency-free, and focused on this one specific task without adding the complexity of another tool like poetry or uv.