[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: how to take a public package private?

On Monday, April 30, 2012 03:45:35 AM Piotr Ożarowski wrote:
> [Ben Finney, 2012-04-30]
> > Paul Elliott <pelliott@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-pro
> >     grams.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)

I want to move the python package openastromod to a private location.

My package, (openastro.org) before modification, when it is still creating a 
public python package, creates: (from dpkg-query -L openastro.org)






So should I not move these to the following places?




or where should the various files be moved to?

I am not sure what to do with the pyshared directory or the correct place for 
the python2.x/dist-packages/openastromod/* files.

openastromod is a module in python that imports an extension called swe.

Paul Elliott                               1(512)837-1096
pelliott@BlackPatchPanel.com               PMB 181, 11900 Metric Blvd Suite J
http://www.free.blackpatchpanel.com/pme/   Austin TX 78758-3117

Attachment: signature.asc
Description: This is a digitally signed message part.

Reply to: