6ae098fe49
Use of `SKChatCompletionAdapter` reliably fails with "'MockValSer' object cannot be converted to 'SchemaSerializer'"; can repro with this example: https://microsoft.github.io/autogen/stable/user-guide/core-user-guide/components/model-clients.html#semantic-kernel-adapter This appears to be related to https://github.com/pydantic/pydantic/issues/7713 - commit uses workaround from https://github.com/pydantic/pydantic/issues/7713#issuecomment-2604574418 ## Why are these changes needed? This unblocks use of the Semantic Kernel integration by addressing the above-referenced error, enabling the integration to perform as expected. ## Related issue number N/A, see https://github.com/pydantic/pydantic/issues/7713 for context, though. ## Checks - [X] I've included any doc changes needed for <https://microsoft.github.io/autogen/>. See <https://github.com/microsoft/autogen/blob/main/CONTRIBUTING.md> to build and test documentation locally. - None needed, internal only change. - [ ] I've added tests (if relevant) corresponding to the changes introduced in this PR. - None added; this works on my machine, but I'm not clear on the root cause of the issue and have no strong opinion on whether this is the ideal way to fix it long term - simply leaning towards PR`ing a tenative fix instead of raising an issue. - [ ] I've made sure all auto checks have passed. - I am not familiar with these, but assume they will be run during CI. --------- Co-authored-by: Leonardo Pinheiro <leosantospinheiro@gmail.com> Co-authored-by: Eric Zhu <ekzhu@users.noreply.github.com>
AutoGen Python packages
This directory works as a single uv workspace containing all project packages. See packages to discover all project packages.
Migrating from 0.2.x?
Please refer to the migration guide for how to migrate your code from 0.2.x to 0.4.x.
Development
TL;DR, run all checks with:
uv sync --all-extras
source .venv/bin/activate
poe check
Setup
uv is a package manager that assists in creating the necessary environment and installing packages to run AutoGen.
Note: To prevent incompatibilities between versions the same UV version as is running in CI should be used. Check the version in CI by looking the setup-uv action, here for example.
For example, to change your version to 0.5.18, run:
uv self update 0.5.18
Virtual Environment
During development, you may need to test changes made to any of the packages.
To do so, create a virtual environment where the AutoGen packages are installed based on the current state of the directory.
Run the following commands at the root level of the Python directory:
uv sync --all-extras
source .venv/bin/activate
uv sync --all-extraswill create a.venvdirectory at the current level and install packages from the current directory along with any other dependencies. Theall-extrasflag adds optional dependencies.source .venv/bin/activateactivates the virtual environment.
Common Tasks
To create a pull request (PR), ensure the following checks are met. You can run each check individually:
- Format:
poe format - Lint:
poe lint - Test:
poe test - Mypy:
poe mypy - Pyright:
poe pyright - Build docs:
poe --directory ./packages/autogen-core/ docs-build - Auto rebuild+serve docs:
poe --directory ./packages/autogen-core/ docs-serve - Check samples in
python/samples:poe samples-code-checkAlternatively, you can run all the checks with: poe check
Note
These need to be run in the virtual environment.
Syncing Dependencies
When you pull new changes, you may need to update the dependencies.
To do so, first make sure you are in the virtual environment, and then in the python directory, run:
uv sync --all-extras
This will update the dependencies in the virtual environment.
Creating a New Package
To create a new package, similar to autogen-core or autogen-chat, use the following:
uv sync --python 3.12
source .venv/bin/activate
cookiecutter ./templates/new-package/