3 ms·
> it’s potentially very slow. Potentially, perhaps. But it's certainly not for the cases where I use it: a pure python package, whose dependencies are already
by pdonis 2y ago
> it’s potentially very slow.
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.
- paulddraper 2y agoI.e. orders of magnitude longer
- pdonis 2y agoOrders of magnitude longer than what?
- the_mitsuhiko 2y agoThan editable installs. The main sentry app takes ~10 seconds to pip install. I would not want to run that every code change. Also more painful to debug because the filenames in the stack trace no longer match to what you have open in your editor.
- pdonis 2y ago> The main sentry app takes ~10 seconds to pip install. 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.
- the_mitsuhiko 2y ago> Why not? If you do a fresh install, everything should match up. Absolutely not. The file names in stack traces will be from the site-packages folder in the venv instead of the local checkout.
- orf 2y agoThat iteration loop is pure madness.
- pdonis 2y agoWhy? It works for me.