Potentially, perhaps. But it's certainly not for the cases where I use it: a pure python package, whose dependencies are already installed and are not changing (only the package itself is). Under those conditions, the command line I gave takes a couple of seconds to run.
Which is much longer than the "couple of seconds" I gave for my use case. Yes, if it takes that long, I can see how you would want some alternative.
> Also more painful to debug because the filenames in the stack trace no longer match to what you have open in your editor.\
Why not? If you do a fresh install, everything should match up. It seems like this problem would be more likely with an editable install, if things aren't kept in sync properly.
Absolutely not. The file names in stack traces will be from the site-packages folder in the venv instead of the local checkout.