You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Feature: Complete TODO items in pet-uv for workspace support #290
The pet-uv crate has incomplete TODO items related to workspace handling that should be addressed for complete uv environment support.
TODO Items
1. crates/pet-uv/src/lib.rs line 142
// TODO: maybe check for workspace in parent folders?
Context: When identifying uv environments, the code doesn't currently look for workspaces in parent directories. This could miss environments that are part of a parent workspace.
2. crates/pet-uv/src/lib.rs line 162
// TODO: check for workspace members/excludes
Context: uv workspaces can have members and excludes patterns. Currently these are not being checked, which could lead to incorrect environment association.
uv Workspace Configuration Reference
From uv documentation, pyproject.toml can contain:
[tool.uv.workspace]
members = ["packages/*"]
exclude = ["packages/excluded"]
Recommended Implementation
When identifying a uv environment, walk up parent directories looking for pyproject.toml with [tool.uv.workspace]
Parse workspace members and exclude globs
Check if current project matches member patterns and doesn't match exclude patterns
Associate environment with the workspace root if applicable
Priority
Medium - Improves accuracy of uv environment detection in monorepo/workspace setups.
Specifically, since PEP 723 allows inline script metadata irrespective of a pyproject.toml, does the script become part of the exclude glob or are they not expected to show up in the resolution at all.
Activity
149segolte commentedon Feb 14, 2026
Quick question for clarification: is uv’s PEP 723 script support (https://docs.astral.sh/uv/guides/scripts/#creating-a-python-script) as documented here: inline script metadata, considered part of this issue, or is that being handled separately?
Specifically, since PEP 723 allows inline script metadata irrespective of a
pyproject.toml, does the script become part of theexcludeglob or are they not expected to show up in the resolution at all.feat: validate uv workspace members/excludes and discover parent work…
feat: validate uv workspace members/excludes and discover parent work…