Package Details: pymacs 0.26-2

Git Clone URL: (read-only, click to copy)
Package Base: pymacs
Description: Interface between Emacs Lisp and Python.
Upstream URL:
Licenses: GPL2
Conflicts: emacs-python-mode
Submitter: xyproto
Maintainer: None
Last Packager: haawda
Votes: 22
Popularity: 0.000000
First Submitted: 2011-12-14 17:07 (UTC)
Last Updated: 2020-04-03 14:37 (UTC)

Latest Comments

1 2 3 Next › Last »

haawda commented on 2012-07-21 19:42 (UTC)

Feel free to do so.

<deleted-account> commented on 2012-07-19 22:17 (UTC)

I think it would be good to separate the package into python2-pymacs and python3-pymacs to follow package naming convention for Python and provide pymacs for both python versions.

haawda commented on 2012-06-30 03:52 (UTC)

Makes sense, applied.

pfeyz commented on 2012-06-29 17:45 (UTC)

I had to add PYTHON=python2 to the second make line in build() to keep this from happening: ... python pppp -C Traceback (most recent call last): ... UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 699: ordinal not in range(128) make: *** [pymacs.pdf] Error 1

ccharles commented on 2012-04-04 13:41 (UTC)

Thanks for all your work, StefanHusmann! Pymacs is a very useful package. Unfortunately this latest version still seems to build with Python 3, even though it is installed in the Python 2 directories. Adding PYTHON=python2 to the first make line in build() fixed that for me.

haawda commented on 2012-04-04 03:36 (UTC)

The change to build with python and python-docutils instead of python2 and python2-docutils was made by design, as can be seen in the comments. But I get a similar problem than yours with pastemacs, which also only works when pymacs is build with python2. So maybe two packages python-pymacs and python2-pymacs would be the best solution, but I would like to maintain only one of them, the one using python2. What do you guys and gals think? In the meanwhile I fall back to python2-deps.

ccharles commented on 2012-04-03 19:41 (UTC)

Hrm, wish I could edit my previous comment... The actual error in *Pymacs* is Traceback (most recent call last): File "<string>", line 1, in <module> ImportError: No module named Pymacs.pymacs Process pymacs exited abnormally with code 1 What I listed before was the result of my own fiddling. This message is what I get with a straight install from AUR.