Summary: | app-emacs/cedet-1.1 and app-editors/emacs-24.1: stale python process | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Martin von Gagern <Martin.vGagern> |
Component: | [OLD] Development | Assignee: | Emacs project <emacs> |
Status: | RESOLVED WORKSFORME | ||
Severity: | normal | ||
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
URL: | https://answers.launchpad.net/python-mode/+question/194157 | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Martin von Gagern
2012-06-15 19:19:27 UTC
Can you report this upstream please? (In reply to comment #1) > Can you report this upstream please? Which upstream? The URL you pasted is for "python-mode.el", which as far as I understand things is using a different code base from the "python.el" shipped with emacs, which is what I'm using now. And both of these are distinct from cedet, aren't they? So which of these should I report this against? 1. Emacs as a whole, using bug-gnu-emacs@gnu.org 2. Dave Love, the original author of python.el, via e-mail 3. The cedet project, via its sourceforge bug tracker 4. Richard Kim, the current maintainer of wisent-python.el, via e-mail 5. Jan Moringen, the most recent copyright-holder of wisent-python.el 6. The python-mode launchpad project, as your URL indicates As far as I can see, one of your two python processes is started by python-mode (from app-emacs/python-mode) when py-start-run-py-shell it non-nil. This should be the same issue as linked in the URL and should be reported to Andreas Roehler. The code that starts the second python process: (In reply to comment #0) > (defcustom-mode-local-semantic-dependency-system-include-path > python-mode semantic-python-dependency-system-include-path > (when (featurep 'python) > (semantic-python-get-system-include-path)) > "The system include path used by Python language.") seems only to be present in stand-alone app-emacs/cedet-1.1. In the CEDET included with Emacs 24.1 this is simply (in cedet/semantic/wisent/python.el): (defcustom-mode-local-semantic-dependency-system-include-path python-mode semantic-python-dependency-system-include-path nil "The system include path used by Python language.") So with the CEDET and progmodes/python.el that are included with Emacs 24.1, the issue shouldn't exist. Could you verify this? (In reply to comment #3) > So with the CEDET and progmodes/python.el that are included with Emacs 24.1, > the issue shouldn't exist. Could you verify this? Sorry it took me so long. Yes, removing the stand-alone cedet package does make the python process go away. I hadn't realized that cedet was included in emacs. Thanks a lot for pointing this out. |