mise-lang-python-packages

Coordinate uv, Poetry, and pipx for Python environments under mise.

1|1|Updated Apr 8, 2026
One-click install
npx skills add https://github.com/ray-manaloto/claude-code-marketplace --skill mise-lang-python-packages
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mise-lang-python-packages
Source: https://github.com/ray-manaloto/claude-code-marketplace/tree/main/mise-toolkit/skills/mise-lang-python-packages
Command: npx skills add https://github.com/ray-manaloto/claude-code-marketplace --skill mise-lang-python-packages

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Managing Python projects often requires juggling multiple tools (uv for per-project environments, poetry for project-level venvs, and pipx for global CLIs) in a non-deterministic way. This Skill clarifies the recommended workflow and how mise coordinates these tools to deliver reproducible environments.

Core Features & Use Cases

  • Unified tool orchestration: Defines how mise pins Python and delegates venv management to uv or Poetry while handling global CLIs with pipx.
  • Clear mixing rules: Prevents cross-tool conflicts by outlining when to use uv, poetry, or pipx in a project.
  • Guided setup: Helps teams adopt a deterministic Python tooling layout for new projects and ongoing maintenance.

Quick Start

Start a new Python project using uv for the environment and pipx for global CLIs, coordinated by mise.

Frequently Asked Questions about mise-lang-python-packages

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I manage Python environments with uv, Poetry, and pipx without conflicts?

Coordinate Python tooling by using mise to pin Python versions, uv for per-project environments, Poetry for project-level venvs, and pipx for global CLIs. This separation prevents cross-tool conflicts and ensures deterministic environments across projects.

What is the best way to use mise for Python package management?

Use mise to pin Python versions while delegating per-project venv management to uv or Poetry, and global CLI tools to pipx. Mise coordinates these tools to deliver reproducible and deterministic Python environments.

When should I use uv versus Poetry for a Python project?

Use uv for per-project environments and Poetry for project-level venvs when specific dependency management features are needed. Clear mixing rules prevent cross-tool conflicts by defining exactly when to use uv, Poetry, or pipx in a project.

Can I use pipx for project dependencies instead of global CLIs?

No, pipx should only manage global CLIs, not project dependencies. Per-project dependencies must be managed by uv or Poetry within isolated venvs. Mixing these tools outside their defined roles creates non-deterministic environments and cross-tool conflicts.

How do I set up a deterministic Python tooling layout for an existing project?

Apply mise to pin the Python version, migrate per-project environments to uv or Poetry, and isolate global CLIs with pipx. This enforces consistent dependency management and deterministic environments for ongoing project maintenance.

Why does mixing Python tools create non-deterministic environments?

Mixing Python tools without coordination creates non-deterministic environments because overlapping dependency management across uv, Poetry, and pipx leads to unresolved conflicts. Mise prevents this by enforcing clear rules for when to use each tool.