Ignoring .venv during script metadata generation
@rubenf I am using
I already have a
1. have
2. point
For #1, adding
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 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 OR2. point
script generate-meatdata right at the requirements.txt?For #1, adding
--excludes '**/.venv/** doesn't workGitHub
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...
