Python: Editable install

[nmccann]

Hi,

I've been trying to set up the project locally (so that I can experiment with not-yet-merged PRs, or make my own changes) and add it as an editable install to my own project, but am not having any luck.

I had followed the DEV_SETUP steps which seem to work correctly for getting the local project working. But then when I navigate to my own project and do:

pip install -e path/to/local/agent-framework

It says it was successful, but doesn't end up with an editable install. In particular, it seems that the nested packages (ex. agent-framework-core, agent-framework-azure etc.) get installed as non-editable, and it seems to use whatever the most recently released version is rather than what I have locally.

I've tried clearing my cache, as well as deleting and recreating my .venv to ensure previous installs aren't causing conflicts.

I'm sure I'm missing something obvious here, and would appreciate any help, thanks!

[eavanvalkenburg]

yeah this can be tricky, you basically need to set the paths for all the packages that you want the local version of. What I've done in the past is use a pyproject.toml with uv and then use this syntax: https://docs.astral.sh/uv/concepts/projects/dependencies/#path the pip native equivalent is quite cumbersome with additional files you need to create

[nmccann]

Appreciate the quick reply, that ended up working for me!

For anyone else trying to do this, I did the following:

• Added a pyproject.toml to my own project (hadn't previously been using uv)
• Converted my requirements.txt over to the pyproject.toml (minus any dependencies that I intended to reference as local editable installs)
• Deleted my existing .venv (may not be necessary, wanted to start with a clean slate though)
• Ran uv venv, then source .venv/bin/activate
• Ran uv add path/to/local/agent-framework
• Ran uv sync to get other dependencies

Then ran my project as usual, but it used the locally checked out version.