This steps include splitting out doctest-mode (and version bump to 0.4, already in overlay), python-mode (already in overlay) and pycomplete. Pycomplete can be included in pymacs, which will make maintenance easier. First, it must be checked if pycomplete works with the Python mode shipped with GNU Emacs, then an integration can be done. Upstream of doctest- and python-mode have been asked to correct warnings and maybe release a new version.
Pycomplete has been forked: http://groups.google.com/group/comp.lang.python/msg/048168c675ff0c68 (called newsgroup now) http://www.emacswiki.org/emacs/pycomplete+.el
Created attachment 181237 [details, diff] Diff between pycomplete.py from Newsgroup and original 1.0
Created attachment 181239 [details, diff] Diff between pycomplete+.el and original 1.0
Created attachment 181240 [details, diff] Diff between newsgroup version and original 1.0 (pycomplete.el) Based on the diffs we have to make a choice between the versions.
(In reply to comment #0) > First, it must be checked if pycomplete works with the Python mode shipped > with GNU Emacs, then an integration can be done. Unfortunately it doesn't work, since it uses functions and variables defined in app-emacs/python-mode, like "py-symbol-near-point" and "py-mode-map". So it should stay with python-mode. Or we follow python-mode upstream and drop pycomplete altogether.
In the tree now.
