Add source roots to the PYTHONPATH in Run Configurations

[ericsua]

Is there a way to add source roots to the PYTHONPATH in Run Configurations, similar to how the Python Run Configurations of PyCharm allow you to do? At the moment, we have to manually add that environment variable for every uv Run Configuration

[InSyncWithFoo]

What is the use case? uv should know where to look for modules on its own.

[ericsua]

For local imports of modules, libraries, and packages. As of now, if I want to import a local module, I have to set the PYTHONPATH environment variable with source roots (the directory marked as Source Roots) to make it work.

[zanieb]

Can you explain why you're not going through build system and virtual environment? PYTHONPATH is sort of a hack, and it's better to use an editable install of your local package if you can.

[ericsua]

I'm using uv to manage dependencies for the virtual environment of a project I'm developing, but I'm not creating a package or library, so I don't install my own modules, nor I need a build system.

For simpler projects, where everything is local and self-contained, I think that's a pretty common approach. In these cases, I use PYTHONPATH to make local imports work without having to restructure or install the code.

Wouldn't it make sense for uv Run Configurations to support this kind of setup more easily, like PyCharm does with content/source roots?

[InSyncWithFoo]

After much consideration, I have decided not to support this. There are two main reasons:

• Run configurations are an alpha-of-alpha feature that might just stop working at anytime. While I don't have a specific plan to remove them (yet), I feel like what I have implemented isn't what I want to stick with in the long term.
• As I envision it, this plugin is supposed to be opinionated towards modern practices. It was designed as such and will continue to be.