pin...@iro.umontreal.ca (François Pinard) writes: > It seems that one problem you met is that Pymacs installs a Python > package, having only pymacs.py besides __init__.py, while you prefer a > single pymacs.py file.
Hi Andreas, and gang. :-) This detail should be over. Pymacs now installs a single Pymacs.py file (after pre-processing it out of Pymacs.py.in), and it does not install a package anymore. I kept the capital (it is Pymacs.py instead of pymacs.py) merely so the documented API does not change at all. While doing this, I saw that the distinction between a file and a package matters at many little places in my code. python-mode has been distributing a single file, while Pymacs code was really written for a package. So, I wonder if Pymacs *ever* worked in python-mode... The commit is now on GitHub (https://github.com/pinard/Pymacs). Hopefully, no Pymacs users will complain about the disappearance of a Pymacs package. It is always possible that someone will reveal a blunt I do not see right now; if this happens, more thinking will be needed. This simplification in Pymacs should ease its usage in python-mode. François P.S. I am a bit sad. After replacing the python-mode bundled in Ubuntu by the one bleeding within launchpad, I did *not* succeed in having it to work for me, earlier today. And my debugging abilities in Emacs are rather dusty. I have to put all of this aside for a little while, because of other duties. As Arnold S. used to say: "I'll be back!" _______________________________________________ Python-mode mailing list Python-mode@python.org http://mail.python.org/mailman/listinfo/python-mode