python-env-manager

Detect the manager from project-root signals first: pixi.toml means pixi, uv.lock means uv, poetry.lock means poetry. Then use only that manager's command, such as pixi add, uv add, or poetry add, never mixing managers in one project.

The package lands in the live environment but not in the manifest, so the next pixi install or poetry install silently removes it. This state divergence is why installs must always go through the project's detected manager.

Install ipython and pyright into a dedicated agent group, then generate pyrightconfig.json with pythonPath pointing at the composed lsp environment's interpreter. Bundled per-manager scripts automate the install, substitution, and verification steps.

Pixi is the default recommendation for fresh projects because it supports composed environments and conda-forge packages. Uv and poetry work well for PyPI-based stacks, while hatch and conda require duplicating dependencies across non-composing environments.

The new dependency was installed into a feature or group that the lsp environment does not compose, so pyright never indexes it. Append the feature to the lsp environment's feature list and re-sync, then run verify_layout.sh to confirm.

Pip with venv has no manifest, no reproducibility, and no shared cache between environments, so installs leave no audit trail. For anything beyond a throwaway script, migrate to a managed alternative like pixi or uv.