How to use live local package without installing to hatch env?

[pmacdonald-tl]

I have a hatch project that has a dependency to another package in our repo. When I "hatch shell", it installs this package to the hatch environment ok using a relative path "../../my_package".
If I update the code in my_package, and run my app, the changes are not synced to the install in my hatch environment (it references the original package copied to the hatch env).
It looks like the hatch-onic way to deal with this is to exit the hatch shell and run "hatch env prune". This is a time consuming and frustrating step to take for every change I make.
Is there another way to reference my_package? eg inserting the path to it in PYTHONPATH?

[ofek]

I have not yet implemented the concept of workspaces which will satisfy this use case. Until then you can set PYTHONPATH in your environments

[pmacdonald-tl]

Thanks Ofek! That works.
Is there any way to skip "syncing dependencies" if I run say "hatch run python"?
I'm testing changes in project-B from project-A (from which I'm running hatch), so I don't need to update any dependencies if I'm testing something explicitly included via PYTHONPATH.

[ofek]

Not yet, but rather than listing a file path dependency you could transition to manual installation with pip in https://hatch.pypa.io/latest/config/environment/overview/#post-install

[pmacdonald-tl]

ok, thanks for the quick replies. Much appreciated!

[pmacdonald-tl]

If anyone is wondering how to set env vars in hatch, you can do this by using the following in your pyproject.toml.

[tool.hatch.envs.default.env-vars]
PYTHONPATH = "<path-to-module>"

This adds a PYTHONPATH env var to your "default" environment.

[pmacdonald-tl]

Worth also noting that you can use a relative path here and it seems to work.

PYTHONPATH = "{root:uri}/../../../../<my_module>"