Re: Help with packaging of python executable and its modules
Hi Julian,
On Fri, Feb 07, 2014 at 02:41:10PM +0100, Julian Taylor wrote:
>
> I assume this is a python application and not a library?
It is an application including some private modules which I like to be
compiled into *.pyc.
> don't install into pyshared, its an implementational detail that might
> eventually go away as its technically not needed anymore since we only have
> one python2 version left.
OK.
> python applications usually get installed into /usr/lib/package-name/ as
> upstream intended
> then you just patch the entry points to add that path to their search path:
You mean something like
$ git diff
diff --git a/debian/install b/debian/install
index 84aa2e1..e6e58ca 100644
--- a/debian/install
+++ b/debian/install
@@ -1,3 +1,3 @@
arden-* usr/bin
-core usr/share/pyshared/arden
+core usr/lib/arden
doc/* usr/share/doc/arden/html
> sys.path.insert(0, 'module-path')
Since I'm not sure whether I understand this, could you please an example
patch for one of the three applications?
> just for completeness, your approach does not work as you are missing a
> __init__.py in the folder
Ahh, Olivier has given the same hint and I can confirm that Olivier's
approach worked - but I would like to get it right in terms of Python
policy. It might be me but I have not found the information you wrote
above in the Wiki or somewhere else. Any hint what I should read to do
it right next time?
Kind regards
Andreas.
--
http://fam-tille.de
Reply to: