Re: Packaging Grip

2016-04-07 Thread Barry Warsaw
On Apr 06, 2016, at 11:48 PM, Scott Kitterman wrote: >In my opinion either can be correct depending on the primary purpose of the >package. I think that's true; take it on a case-by-case basis. In general, I like having a separate binary package for the /usr/bin script because it can be more eas

Re: Packaging Grip

2016-04-07 Thread Dmitry Shachnev
Hi Tiago, On Wed, Apr 06, 2016 at 11:37:24PM -0300, Tiago Ilieve wrote: > Thanks for taking the time to explain me this, but actually I got a > little bit confused. Because yes, what you said is consistent with > what I found on articles about Python packaging on wiki.d.o[1][2], but > at the same

Re: Packaging Grip

2016-04-06 Thread Scott Kitterman
On April 6, 2016 10:37:24 PM EDT, Tiago Ilieve wrote: >Hi Dmitry, > >On 6 April 2016 at 17:21, Dmitry Shachnev wrote: >> 1. Public (/usr/lib/python*/dist-packages) vs private (/usr/share/) >location >> depends on whether the module is intended to be used by third-party >packages, >> or only by

Re: Packaging Grip

2016-04-06 Thread Tiago Ilieve
Hi Dmitry, On 6 April 2016 at 17:21, Dmitry Shachnev wrote: > 1. Public (/usr/lib/python*/dist-packages) vs private (/usr/share/) location > depends on whether the module is intended to be used by third-party packages, > or only by grip itself. > > 2. The Style Guide doesn't *require* both Python

Re: Packaging Grip

2016-04-06 Thread Dmitry Shachnev
Hi Tiago, On Mon, Apr 04, 2016 at 04:29:44PM -0300, Tiago Ilieve wrote: > Hi, > > The Style Guide for Packaging Python Libraries[1] states that in cases > like this, one should package the library for both Python 2 and 3, > creating a third package that contains the executable. As this package > i

Re: Packaging Grip

2016-04-04 Thread Tiago Ilieve
Hi, The Style Guide for Packaging Python Libraries[1] states that in cases like this, one should package the library for both Python 2 and 3, creating a third package that contains the executable. As this package is indeed intended to be used as a CLI application (as its description says), I've fo

Packaging Grip

2016-04-01 Thread Tiago Ilieve
Hi, I'm packaging grip[1] (ITP #790611[2]) and have a few doubts: Should I package it as an application or a library? It is really a CLI application, but when called it imports its main function as a module[3]. I can't use its entry point script directly because it expects to be insta