Re: Correct location of .py and .pyc files
On Wed, Nov 12, 2003 at 02:32:30PM -0500, Marco Paganini wrote:
> - According to Python's Policy, section 3.1.1, private modules should be
> installed in /usr/lib/site-python/module, /usr/lib/pythonX.Y/site-packages/module
> or /usr/lib/package. In my case, it makes more sense to install them
> under /usr/lib/package, as they're private.
>
> - I should bytecompile the modules at installation time. This matches my
> original expectations. However, the Python Policy is not clear about
> where I should put the byte-compiled files. Is /usr/lib/package an
> acceptable place? It would sure be nice to keep them together with
> their "source" counterparts.
Well, that path sounds fine at least for what FHS is concerned, so if the
Python Policy draft doesn't clarify, I guess it's ok.
> Another question: My application has some "skeleton" files that are copied
> to the user's home directory by an installation program. Robert Millan (my
> Debian guru, in the Cc:) has recommended /usr/share/doc/package/something,
> but I'd like to keep those out of the documentation tree. Is there any other
> place where I should put those?
That was "/usr/share/doc/package/examples". I'm not sure if it's formalised
in Policy or FHS, but at the least is the normal tendency and I'd suggest to
follow it.
--
Robert Millan
"[..] but the delight and pride of Aule is in the deed of making, and in the
thing made, and neither in possession nor in his own mastery; wherefore he
gives and hoards not, and is free from care, passing ever on to some new work."
-- J.R.R.T, Ainulindale (Silmarillion)
Reply to: