[Ben Finney, 2012-04-30] > Paul Elliott <pelli...@blackpatchpanel.com> writes: > > > My package uses a package that it makes public. What is the standard, > > established way to take that package private? > > In the absence of better-informed answers (please, knowledgeable Debian > Python people, help us out with this information!): > > The Debian Python Policy says: > > A program using /usr/bin/python as interpreter can come up with > private Python modules. These modules should be installed in > /usr/share/module, or /usr/lib/module if the modules are > architecture-dependent (e.g. extensions). > > > <URL:http://www.debian.org/doc/packaging-manuals/python-policy/ch-programs.html#s-current_version_progs>
I will change that to /usr/share/package-name/module and /usr/lib/package-name/module if no one objects (adding /usr/share or /usr/lib to sys.path is not a good idea, we don't do that so policy should be updated) -- Piotr Ożarowski Debian GNU/Linux Developer www.ozarowski.pl www.griffith.cc www.debian.org GPG Fingerprint: 1D2F A898 58DA AF62 1786 2DF7 AEF6 F1A2 A745 7645 -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120430084534.gi3...@piotro.eu
