load-extended-executes fails when py-install-directory is not set

[Felix Geller]

If `py-install-directory' is not set, the current logic looks for "/python-extended-executes.el" when it should be "python-extended-executes.el". The attached patch (against rev 836) is a primitive remedy :)

[Andreas Roehler (a-roehler)]

Am 15.02.2012 00:12, schrieb Felix Geller:
> Public bug reported:
>
> If `py-install-directory' is not set, the current logic looks for
> "/python-extended-executes.el" when it should be "python-extended-
> executes.el". The attached patch (against rev 836) is a primitive remedy
> :)
>

Hi Felix,

thanks pointing at the matter.

AFAIU there is no way to avoid giving just one name where to
install/load from.

Tried in the past several workarounds same kind you sent, however, it
turned out never stable.

It might help if you can tell the reasons, why `py-install-directory'
was not set.

A solution would be rather providing a workaround giving
`py-install-directory' a default value, then fixing the loading of
single files.

OTOH probably it's better to get an `py-install-directory'-not-set-error
than loading from uncertain guesses.

So far, thanks again,

Andreas

[Andreas Roehler (a-roehler)]

code is merged into python-mode.el, so this issue is fixed as a side-effect :)

[Felix Geller (fgeller)]

Different approach now -- use different implementation of py-guess-py-install-dir (uses locate-library) and use it if py-install-dir is not set.

The recent version (837) still exhibited the save problem for me. The patch is against r837.

[Andreas Roehler (a-roehler)]

Hi Felix,

applied, thanks.
Please re-open this report should be something left.

Andreas