https://wikemacs.org/index.php?action=history&feed=atom&title=Python_libraries 2026-05-01T22:54:14Z Revision history for this page on the wiki MediaWiki 1.35.14 https://wikemacs.org/index.php?title=Python_libraries&diff=47800&oldid=prev 2017-05-04T14:58:37Z

<p>easy install and use of python packages in their venv</p> <p><b>New page</b></p><div>Here we'll take notes on libraries and best practices on how to write Emacs packages that use Python tools (like Elpy).<br /> <br /> = Libraries =<br /> <br /> == Install and access pip dependencies in their own virtual env with python-environment ==<br /> <br /> Let's say you write an Emacs plugin which uses Python scripts. Then you would want to setup Python modules for that script easily from Emacs. This is the problem [https://github.com/tkf/emacs-python-environment emacs-python-environment] solves, an important and recurrent problem in emacs packages using python tools.<br /> <br /> For example, [[Elpy]] relies on a few python dependencies, found in pypi: jedi, yapf, importmagic, etc. When we install Elpy we must install them too. And where should we do it ? Python's best practices tell us to do so in our virtual env. Fine, but as soon as we switch to another project, we should install them again in this other venv. We could install them globally, but then we need to modify the creation of our virtual envs, that by default do *not* use system-wide packages. We could… well, it's cumbersome. This package solves that.<br /> <br /> It's actually simple to use. For an example, see [https://github.com/abingham/emacs-traad emacs-traad].<br /> <br /> <br /> [[Category:Programming languages]]<br /> [[Category:Programming]]<br /> [[Category:Python]]<br /> [[Category:Tutorial]]</div>

Elvince