M-x pyvenv-activate <RET> ~/Documents/bitbucket-python-scripts/.env353 <RET>
works fine. Elpy Config buffer confirms that.
However with the following in ~/.emacs file
(require 'package) (add-to-list 'package-archives '("melpa-stable" . "https://stable.melpa.org/packages/")) (package-initialize) (advice-add 'python-mode :before 'elpy-enable) (elpy-enable) (custom-set-variables '(elpy-rpc-python-command "python3") '(python-shell-interpreter "python3") '(pyvenv-activate "~/Documents/bitbucket-python-scripts/.env353"))
when I start Emacs and
I see in the Elpy Config buffer that the virtual environment is not set. custom-set-variables were generated by Customization option of Emacs
Please point out my error.
Using: Elpy 1.28.1 Emacs 24.5.1 Debian GNU/Linux 9.8 (stretch)
In ~/.emacs just after (elpy-enable) properly activate the virtual environment .env353. I have no idea why custom-set-variable command (obtained through customization) doesn't work.