ssbb / pyenv-mode-auto

Automatically activates pyenv version within Emacs if .python-version file exists.

pyenv-mode-auto

Automatically activate pyenv version from Emacs with pyenv-mode.

It traverse directories up until .python-version file will be found and activates pyenv version defined there.

Installation

You can simply install package from Melpa.

(add-to-list 'package-archives
       '("melpa" . "http://melpa.org/packages/") t)

And then M-x package-install [RET] pyenv-mode-auto [RET]. After Installing you should require this package:

(require 'pyenv-mode-auto)

Usage

Just open any file within you project (with .python-version file in the same directory or above) and you pyenv version will be activated.

pyenv-mode-auto's Issues

Question : Is this replacement for pyvenv-workon ?

I was earlier using pyvenv and when I manually set pyvenv-workon to the same virtualenv, everything used to work, but there was always this manual step to select the virtualenv. So I came here looking for "automation"

I (think) I have installed pyenv-mode-auto correctly (It is really simple) yet, I am not sure it is working for me.
.python-version exists in the parent folder of the file I have opened.

To troubleshoot, I even manually pyenv-mode-set to the correct virtualenv - yet after doing that M-! which python reports /usr/local/bin/python not the one from my virtualenv.

What am I doing wrong ? (or may be I am expecting something that is not supposed to work)

Also, what are the steps to troubleshoot ?

Link to blog post in README is broken

This link in the README is 404:
http://ssbb.me/posts/emacs-pyenv-auto-activation-en/

Thanks.

License

Hey,

I'd like to contribute a couple of patches to the code, but my employer requires that the projects have a license. Would you considerer adding a license explicitly to the project?

Thanks!

Support multiple active environments

Currently, pyenv-mode-auto assumes that any .python-version file will contain one line with one active version. However, pyenv allows for the cascade of environments (I presume via the shims looking through one and falling back to the next configured environment if a given command doesn't exist in the first environment, but I have not checked this). This cascading setup is relatively common for tox-oriented workflows, but currently breaks pyenv-mode-auto.

I'm not sure how such a simple library could emulate this behavior fully, but I have a small change that fixes it in all of my cases: simply activate the first listed environment.

This looks as follows:

(defun pyenv-mode-auto-hook ()
  "Automatically activates pyenv version if .python-version file exists."
  (f-traverse-upwards
   (lambda (path)
     (let ((pyenv-version-path (f-expand ".python-version" path)))
       (if (f-exists? pyenv-version-path)
           (progn
             (pyenv-mode-set (car (s-lines (s-trim (f-read-text pyenv-version-path 'utf-8)))))
             t))))))

Note the addition of the use of car and s-lines.

If you'd like, I'll happily work this into a PR. I wanted to open the floor for some discussion before I did that, however.

Format of the .python-version file

I am trying to use this package for my python development on emacs.
I have a .python-version file inside my project folder, at the same level as the source code I am working on. This is the content of the .python-version file, a one-liner that indicates the location of the pinns virtual environment that I want to use for my code.

/home/dromero/.virtualenvs/pinns

However, the pyenv-mode-auto package does not automatically activate this environment.
Can you please help? What am I doing wrong?

Thanks!