Summary
When dev-clone is executed, it calls mkproject, which in turn triggers the postmkproject hook from virtualenvwrapper. In the onboarding process it asks to set this file up.
This behaviour is undesirable for developers who do not use VS Code, as it litters the project's parent directory with unnecessary configuration files. I propose adding a new flag to the dev-clone script, such as --no-workspace, that skips the creation of this IDE-specific file.
Summary
When dev-clone is executed, it calls
mkproject, which in turn triggers thepostmkprojecthook fromvirtualenvwrapper. In the onboarding process it asks to set this file up.This behaviour is undesirable for developers who do not use VS Code, as it litters the project's parent directory with unnecessary configuration files. I propose adding a new flag to the
dev-clonescript, such as--no-workspace, that skips the creation of this IDE-specific file.