mirror of
https://github.com/microsoft/autogen.git
synced 2025-08-20 06:31:54 +00:00
317d5d03ec
* first commit * use_ocr flag * initial refactor * test * small fixes * adding animations, in progress * red boundary animations * add hover tool * fix timeout time - reduces a lot of errors * put prompts in separate file * prompt organize * add cursor animation * format and checks pass * added check for reset
AutoGen Python packages
See autogen-core package for main functionality.
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.
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-serveAlternatively, you can run all the checks with: poe check
Note
These need to be run 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
source .venv/bin/activate
cookiecutter ./templates/new-package/