Consider tagging a new release about emacs-direnv

[wbolster]

oops, i actually did bump the version 1.3.0 (and tag it) last week, for exactly the reason you described:
https://github.com/wbolster/emacs-direnv#history

turns out i forgot to push the tag to github, which i just did:

To github.com:wbolster/emacs-direnv.git
 * [new tag]         1.3.0 -> 1.3.0

the next melpa stable build should have it. this usually takes a few hours.

[wbolster]

anyway, since you're into emacs-python-pytest and direnv-mode (both of which i wrote), let me know how it goes since i'm eager to learn from others having similar workflows as i do. :)

[ccharles]

Thanks for the quick fix!

I didn't realize you also wrote emacs-python-pytest, but I guess that explains why its README references direnv-mode 😄. I'll update my local package and try it out.

[wbolster]

heh. direnv is fantastic and solves all my ‘path problems’. i wanted that in emacs as well, hence direnv-mode. 🌳

and since python-pytest.el needs correct execution paths as well, i decided to put a recommendation in the readme.