[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Inconsistency in source package naming for python modules



On Jul 11, 2013, at 03:54 AM, Thomas Goirand wrote:

>Ok, so let's not use the word "rule" but call it "guide-line", and for
>future packages only (I have *never* proposed to change already uploaded
>packages). Do you feel more comfortable now? :)

Does your response mean you disagree with my suggested recommendation?

Also, did you see the code I posted a link to previously?

$ python wid.py -u debian configglue
import path: /usr/lib/python2.7/dist-packages/configglue/__init__.py
Binary/source in Debian: python-configglue

 python-configglue | 1.0-1 | wheezy | source, all
 python-configglue | 1.0-1 | jessie | source, all
 python-configglue | 1.0-1 | sid    | source, all

$ python3 wid.py -u debian flufl.enum
import path: /usr/lib/python3/dist-packages/flufl/enum/__init__.py
Binary in Debian: python3-flufl.enum

 python3-flufl.enum | 3.3.2-1 | wheezy | all
 python3-flufl.enum | 3.3.2-1 | jessie | all
 python3-flufl.enum | 3.3.2-1 | sid    | all

Source in Debian: flufl.enum

 flufl.enum | 3.3.2-1 | wheezy | source
 flufl.enum | 3.3.2-1 | jessie | source
 flufl.enum | 3.3.2-1 | sid    | source


Of course, the one limitation is that the package has to be already installed
and importable.

-Barry


Reply to: