Hi @JaeAeich 👋

I noticed the postCreateCommand in your solution always deletes the existing .venv and creates a new one, which will result in reinstalling dependencies every time. This could slow down the setup process unnecessarily.

I recommend using this alternative approach:

"postCreateCommand": "[ -d .venv ] || make venv && . .venv/bin/activate && make install"

This checks if the .venv directory already exists and reuses it if available. If it doesn’t exist, it will create the virtual environment and install dependencies.

This way, we avoid recreating the virtual environment every time, which should help save time, especially when dependencies are already in place. What do you think?

fix: check existing venv before creating venv #64

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions