On 07/08/2013 10:10 PM, Scott Kitterman wrote:
> There is no policy on this either way, so there's no "mistake".
Well, the mistake is precisely to have no rule, IMO.
On 07/08/2013 11:37 PM, Barry Warsaw wrote:
> Hopefully, it will become more and more common to have at least
> python-X and python
Another rule of thumb I use is that if a project is not just about python
module but also provides some GUI or CUI interface which might be used by users
without realizing presence of a python behind I do not prefix with python-, eg
psychopy.
Sandro Tosi wrote:
>On Mon, Jul 8, 2013 at 4:10 PM
On Mon, Jul 8, 2013 at 4:10 PM, Scott Kitterman wrote:
> There is no policy on this either way, so there's no "mistake". Personally, I
> tend to use the upstream name for the source package name and
> python-$modulename (per Python policy) for the binary.
I'm using the same same rule, with just
3 matches
Mail list logo
