Re: Tool support for private modules
> If the policy recommends that packages be set up a particular way
> ("put package-specific modules in '/usr/share/package/'"), but the
> standard tools behave differently ("put all modules by default in
> '/usr/lib/pythonX.Y/site-packages/'"), then there's a step that needs
> to be taken to get from the default behaviour to the behaviour
> recommended by policy.
The standard tools Do it right. So there must be a bug somewhere in your
packaging or upstream's source. Unfortunately this bug is not shown in
my fishbowl.
You can read trough http://wiki.debian.org/DebianPython/NewPolicy and
check if your packaging contains all the pieces mentioned there. If you
think it does, show your code.
--
Bernd Zeimetz
<bernd@bzed.de> <http://bzed.de/>
Reply to: