github-featured/microsoft--agent-framework
2
0
Fork 0
Code Issues Pull Requests Deployments Models Agent Notes Packages Projects Releases Wiki Activity

Python: Clean up dependency groups and compatibility (#7046)

Browse Source 
* Python: Clean up dependency management

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Copilot-Session: 2f7b1c89-f3ff-418d-ab4e-4f014fda308f

* Python: Harden Mistral SDK import fallback

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Copilot-Session: 2f7b1c89-f3ff-418d-ab4e-4f014fda308f
This commit is contained in:
Eduard van Valkenburg
2026-07-11 00:40:42 +02:00
committed by GitHub
parent 875031ff56
commit 68136ee081
53 changed files with 1598 additions and 1505 deletions
Download Patch File Download Diff File Expand all files Collapse all files
python/.github/skills/python-package-management/SKILL.md
Vendored
+6 -2
View File
@@ -42,7 +42,7 @@ uv run poe venv --python 3.12
# Intentionally upgrade a specific dependency to reduce lockfile conflicts
uv lock --upgrade-package <dependency-name> && uv run poe install
# Refresh all dev dependency pins, lockfile, and validation in one run
# Refresh exact development dependency-group pins, lockfile, and validation in one run
uv run poe upgrade-dev-dependencies
# First, run workspace-wide lower/upper compatibility gates
@@ -69,7 +69,11 @@ uv run poe add-dependency-and-validate-bounds --package core --dependency "<depe
- For dependency changes, run workspace-wide bound gates first, then `validate-dependency-bounds-project --mode both` for the target package/dependency to keep minimum and maximum constraints current. The same task can also drive repo-wide upper-bound automation by using `--package "*"` and omitting `--dependency`.
- Prefer targeted lock updates with `uv lock --upgrade-package <dependency-name>` to reduce `uv.lock` merge conflicts.
- Use `add-dependency-and-validate-bounds` for package-scoped dependency additions plus bound validation in one command.
- Use `upgrade-dev-dependencies` for repo-wide dev tooling refreshes; it repins dev dependencies, refreshes `uv.lock`, and reruns `check`, `typing`, and `test`.
- Keep shared tooling and source/type-check support in the root or package `dev` group. Put package-specific test
fixtures in a `test` group, and use a feature-named group for local-only executable dependencies that cannot be
expressed in published runtime metadata.
- Use `upgrade-dev-dependencies` for repo-wide development dependency refreshes; it repins exact dependencies
across development groups, refreshes `uv.lock`, and reruns `check`, `typing`, and `test`.
## Lazy Loading Pattern