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

2015-09-02 Thread Robert Collins
On 2 September 2015 at 20:35, Ben Finney wrote: > Ben Finney writes: > According to Robert's earlier message, that means the Distutils > metadata file needs to be not in the application's private directory, > but in a directory on

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

2015-09-02 Thread Karsten Hilbert
On Wed, Sep 02, 2015 at 09:06:01PM +1200, Robert Collins wrote: > > Ben Finney writes: > > > According to Robert's earlier message, that means the Distutils > > metadata file needs to be not in the application's private directory, > > but in a directory on the

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

2015-09-02 Thread Ben Finney
Ben Finney writes: > 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've made a real, minimal example of a Debian package of a Python

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

2015-09-02 Thread Piotr Ożarowski
> * The ‘--install-scripts’ option is *not* used, because Distutils places > the constructed scripts in the correct directory (‘/usr/bin/’) by > default. and that's why it doesn't work. As I already suggested in my previous mail, installing scripts into private directory and symlinking them

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

2015-09-02 Thread Robert Collins
On 2 September 2015 at 22:45, Ben Finney wrote: > Robert Collins writes: > >> That private directory must be on the python search path when running >> the application (or the modules can't be imported). > > Not at all. The application's

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

2015-09-02 Thread Robert Collins
On 2 September 2015 at 21:19, Karsten Hilbert wrote: > On Wed, Sep 02, 2015 at 09:06:01PM +1200, Robert Collins wrote: > >> > Ben Finney writes: >> >> > According to Robert's earlier message, that means the Distutils >> > metadata file

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

2015-09-02 Thread Barry Warsaw
On Sep 02, 2015, at 09:06 PM, Robert Collins wrote: >So this is perhaps the disconnect: I did not say the metadata should >move: it should be in the private directory - it has to be adjacent to >the packages/modules its describing, since if it is present but the >package/module is not that is at

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

2015-09-02 Thread Barry Warsaw
On Sep 02, 2015, at 11:19 AM, Karsten Hilbert wrote: >> That private directory must be on the python search path > >Maybe I'm a bit dense but isn't that what OP very much >DOESN'T want to _happen_ ? Not on the default sys.path, sure. But it has to get on sys.path at some point before the

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

2015-09-02 Thread Ben Finney
Robert Collins writes: > That private directory must be on the python search path when running > the application (or the modules can't be imported). Not at all. The application's private modules are imported only via relative imports. -- \ “Free thought is a