Ignoring .venv during script metadata generation

tl_jacob · 2025-04-29T19:42:17.487Z

@rubenf I am using `uv` for local script development, which creates a `.venv` directory within the script directory. I noticed that `script generate-metadata` was taking a long time > 40sec for a single script and was able to determine that the bottleneck is [findGlobalDeps](https://github.com/windmill-labs/windmill/blob/75ee10ea65a391701875450fd0454eba93315037/cli/script.ts#L871) iterating over all the files in the `.venv` directory when trying to find a lockfile candidate. I already have a `requirements.txt` right next to the script. Is there a way to either: 1. have `script generate-metadata` ignore the `.venv` directory OR 2. point `script generate-meatdata` right at the `requirements.txt`? For #1, adding `--excludes '**/.venv/**` doesn't work

@rubenf I am using

uv

uv

for local script development, which creates a

.venv

.venv

directory within the script directory. I noticed that

script generate-metadata

script generate-metadata

was taking a long time > 40sec for a single script and was able to determine that the bottleneck is findGlobalDeps iterating over all the files in the

.venv

.venv

directory when trying to find a lockfile candidate.

I already have a

requirements.txt

requirements.txt

right next to the script. Is there a way to either:
1. have

script generate-metadata

script generate-metadata

ignore the

.venv

.venv

directory OR
2. point

script generate-meatdata

script generate-meatdata

right at the

requirements.txt

requirements.txt

?

For #1, adding

--excludes '**/.venv/**

--excludes '**/.venv/**

doesn't work

GitHub

windmill/cli/script.ts at 75ee10ea65a391701875450fd0454eba93315037 ...

Open-source developer platform to power your entire infra and turn scripts into webhooks, workflows and UIs. Fastest workflow engine (13x vs Airflow). Open-source alternative to Retool and Temporal...

Ignoring .venv during script metadata generation

Similar Threads