Package Details: emacs-elpy 1.35.0-1

Git Clone URL: (read-only, click to copy)
Package Base: emacs-elpy
Description: Emacs Python Development Environment
Upstream URL:
Licenses: GPL3
Submitter: WhittlesJr
Maintainer: Geballin
Last Packager: Geballin
Votes: 2
Popularity: 0.000000
First Submitted: 2017-05-30 22:53 (UTC)
Last Updated: 2021-03-18 22:39 (UTC)

Latest Comments

WhittlesJr commented on 2017-06-03 16:06 (UTC)

If anyone reads this and wants the answer to the aforementioned mystery: it was some strange interaction between pacaur and the user account. I tried using yaourt on that account and everything worked as expected. (I'm using these helpers mainly for Ansible automation)

WhittlesJr commented on 2017-05-31 03:44 (UTC)

This is for the actual emacs package (the elisp files), and is dependant on python-elpy. Python-elpy only installs the python package associated with the project, although both point to the same git repo. As for my comments: although still a mystery to me, I found that the wrong permissions I was getting seem to be associated with the extra user account I was using to install python packages from the AUR (via pacaur.) When I install with my regular user, they get the right permissions. Same umask and everything... And only for AUR packages that don't specify the file mode in the package step. Still looking into that. Not sure if it could be addressed by using explicit permissions somehow in the pkgbuilds, but for now I'll call it an issue on my end.

chendaniely commented on 2017-05-31 02:06 (UTC) (edited on 2017-05-31 02:09 (UTC) by chendaniely)

how is this different from the python-elpy package? I've seen some of the comments from WhittlesJr in the python-elpy package thread, Is this fixing the issues you brought up there because that other package was not being maintained?