Package Details: pymacs 0.25-2

Git Clone URL: https://aur.archlinux.org/pymacs.git (read-only)
Package Base: pymacs
Description: Interface between Emacs Lisp and Python.
Upstream URL: http://pymacs.progiciels-bpi.ca/
Licenses: GPL2
Conflicts: emacs-python-mode
Submitter: xyproto
Maintainer: vorbote
Last Packager: vorbote
Votes: 23
Popularity: 0.242851
First Submitted: 2011-12-14 17:07
Last Updated: 2015-07-07 21:47

Latest Comments

haawda commented on 2012-07-21 19:42

Feel free to do so.

Anonymous comment on 2012-07-19 22:17

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

Makes sense, applied.

pfeyz commented on 2012-06-29 17:45

I had to add PYTHON=python2 to the second make line in build() to keep this from happening:

...
python pppp -C ppppconfig.py pymacs.rst.in
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

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

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

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.

ccharles commented on 2012-04-03 18:36

StefanHusmann, do you mean that the solution to my problem is contained in the comments below, or that you are experiencing the same problem as I am?

I don't see a solution below.

ccharles commented on 2012-04-03 18:30

StefanHusmann, do you mean that the solution to my problem is contained in the comments below, or that you are experiencing the same problem as I am?

I don't see a solution below.

ccharles commented on 2012-04-03 18:28

StefanHusmann, do you mean that the solution to my problem is contained in the comments below, or that you are experiencing the same problem as I am?

I don't see a solution below.

All comments