Application libraries private, Distutils metadata available for console scripts and introspection

Howdy all, How can I specify to Pybuild that an application should have its modules all in a private namespace, but have the Distutils metadata also available to `pkg_resources` queries? I install its libraries to an application-specific space with `PYBUILD_INSTALL_ARGS =

Install libraries to a private directory, with Debhelper, Pybuild, dh_python2, dh_python3

Howdy all, The Python packaging page at the Debian wiki says of private libraries: Private modules should be installed in private directory such as /usr/share/packagename/ or /usr/lib/packagename/ […] Example 2: Python application […] Add these three lines:

Re: Application libraries private, Distutils metadata available for console scripts and introspection

PKG resources should find it anywhere in the python path. I'd the path correct within the all processes? On 1 Sep 2015 2:53 pm, "Ben Finney" wrote: > Howdy all, > > How can I specify to Pybuild that an application should have its modules > all in a private namespace,

Re: Application libraries private, Distutils metadata available for console scripts and introspection

Robert Collins writes: > PKG resources should find it anywhere in the python path. That's exactly the point, though. The packages are private to this application, and should not be available for import by other programs. On the other hand, the Distutils metadata (the