Daniel Hahler
Daniel Hahler
FWIW, I have currently disabled the pyenv-virtualenv hook, and use [smartcd](https://github.com/cxreg/smartcd) to activate the virtualenv with `pyenv virtualenv foo` (besides other things) when entering the project dir.
I've thought there was maybe some central point where pyenv determined which version should be used. Then there could a check get added which compares it with the last used...
@obestwalter I would recommend https://github.com/Tarrasch/zsh-autoenv by now, after having a lot of features to it a while ago. It also supports unloading (even very comfortably via `autostash`).
Yeah, it's pretty off topic, but interesting in general. direnv looks really nice, and I would have probably used it instead of rewriting/enhancing zsh-autoenv, if I've known about it already....
related: https://github.com/spulec/freezegun/issues/463
Interesting, but rather complex (from a quick look). Do you expect the transformation function to figure out what test (file) needs to run for some changed code? Do you know...
@dacodekid Just curious: why do you use `TEST_RUNNER`. It is easier to run just `pytest` by itself. Check out https://github.com/jezdez/envdir/ for env(dir) handling.
It turns out that `notifier.stop()` needs to be called on reload: https://github.com/copton/react/pull/1/files Would it be possible for pyinotify to handle this, when the old notifier reference gets overwritten / garbage...
@timabbott can you try https://github.com/seb-m/pyinotify/pull/96?
Makes sense. Do you have tried to create a patch for this yourself by any chance already?