diff options
| author | spalax <spalax@web> | 2015-05-21 12:28:33 -0400 |
|---|---|---|
| committer | admin <admin@branchable.com> | 2015-05-21 12:28:33 -0400 |
| commit | 9ee5f1626e6ebf04479b761fa479fc340693204c (patch) | |
| tree | afc58f7d7d872b47d8b7ab4fb47c1b06fa7eb3fa | |
| parent | b385373b69d55e466e2a4186bce2967626b2a33e (diff) | |
| download | ikiwiki-9ee5f1626e6ebf04479b761fa479fc340693204c.tar ikiwiki-9ee5f1626e6ebf04479b761fa479fc340693204c.tar.gz | |
Question about python path for external plugins.
| -rw-r--r-- | doc/todo/location_of_external_plugins.mdwn | 8 |
1 files changed, 8 insertions, 0 deletions
diff --git a/doc/todo/location_of_external_plugins.mdwn b/doc/todo/location_of_external_plugins.mdwn index c28003e74..09f61da95 100644 --- a/doc/todo/location_of_external_plugins.mdwn +++ b/doc/todo/location_of_external_plugins.mdwn @@ -22,3 +22,11 @@ As a side note, the accompanying proxy.py might better be placed into some direc >> external plugins means it's automatically in their `sys.path` without >> needing special configuration. --[[smcv]] >> (a mostly-inactive member of Debian's Python modules packaging team) + +>>> I mostly agree, but a problem arises when the external plugin we are using is not located in the same directory as the `proxy.py` file, but in a directory somewhere in a `libdir` or `libdirs` directory. Right now (for a soon-to-be published plugin I am working on) the solutions I am thinking about are: +>>> +>>> - Call ikiwiki using ``PYTHONPATH="$PYTHONPATH:/usr/lib/ikiwiki/plugins ikiwiki ...``, but it is a pain to write this each time I want to use this (and any solution like creating a custom script do not seem very nice); +>>> - Make my plugin add `/usr/lib/ikiwiki/plugins` to its python path, but I do not know how portable this is for a non Debian distribution. +>>> +>>> Any better idea (and sorry for digging up an old post). +>>> -- [[Louis|spalax]] |