Re: Inconsistency in source package naming for python modules

2013-07-08 Thread Barry Warsaw
On Jul 08, 2013, at 09:59 PM, Thomas Goirand wrote: >Over the last months, I've seen lots of inconsistency in the source >package naming scheme in the python module maintained in the team. >Sometimes, module X will have its source package called python-X or just X. > >If we have a python module na

Re: Inconsistency in source package naming for python modules

2013-07-08 Thread Simon Chopin
Quoting Thomas Goirand (2013-07-08 15:59:02) > Hi, > > Over the last months, I've seen lots of inconsistency in the source > package naming scheme in the python module maintained in the team. > Sometimes, module X will have its source package called python-X or just X. > > If we have a python mod

Re: Inconsistency in source package naming for python modules

2013-07-08 Thread Scott Kitterman
On Monday, July 08, 2013 09:59:02 PM Thomas Goirand wrote: > Hi, > > Over the last months, I've seen lots of inconsistency in the source > package naming scheme in the python module maintained in the team. > Sometimes, module X will have its source package called python-X or just X. > > If we hav

Inconsistency in source package naming for python modules

2013-07-08 Thread Thomas Goirand
Hi, Over the last months, I've seen lots of inconsistency in the source package naming scheme in the python module maintained in the team. Sometimes, module X will have its source package called python-X or just X. If we have a python module named X, then IMO, we should stick to call the source p