Comment 3 for bug 916166

Hi Andreas,

Yes, afraid it's still there. There's a minor problem with the load path, but the attached patch fixes it (also includes another expand-file-name). More seriously, the inferior python still can't import Pymacs.pymacs because there's no __init__.py in .../Pymacs (perhaps you did bzr add __init__.py?), but also because Emacs thinks it's in the python-mode/completion so the import Pymacs/pymacs fails.

This patch communicates the py-install-dir to python via a new environment variable and sets the python path with that. This seems to work for me and the Python that I'm finding with C-x C-f is loaded, but the buffer remains as the buffer visible when I did C-x C-f. If this is the *scratch* buffer then there's a message 'The mode `Text' does not support Imenu' and if the buffer happens to be another file under version control, emacs runs the version control check again as if I had found that file. I don't know what's causing that.

Hope this is useful.

Best,
Richard.

On 21 Jan 2012, at 20:46, Andreas Roehler wrote:

> Do you have that problem still?
> Please re-open if yes.
>
> Cheers,
>
> Andreas
>
> ** Changed in: python-mode
> Status: In Progress => Fix Committed
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/916166
>
> Title:
> pycomplete.el buffer not deleted
>
> Status in An Emacs mode for editing Python code:
> Fix Committed
>
> Bug description:
>>
>> Also, with py-load-pymacs-p non-nil whenever I open a new .py file, pycomplete.el is also opened and the pycomplete.el buffer is presented instead of the actual file buffer. I see that pycomplete.el should be loaded, evaluated and the buffer killed, but it is not being killed for me -- perhaps because of the import failure above?
>>
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/python-mode/+bug/916166/+subscriptions