Re: [Python-modules-commits] [python-cpuinfo] 02/02: Import Debian changes 3.0.0-1

[Ghislain Vaillant <ghisvail@gmail.com>]

Also, the `cpuinfo` utility can be invoked with `python[3] -m cpuinfo` 
according to the upstream README [1]. So, I am not convinced of the 
benefit of introducing an additional binary package (py-cpuinfo) for 
something the library packages already provide.

[1] https://github.com/workhorsy/py-cpuinfo#run-as-a-module

Ghis


On 16/04/17 16:24, Sandro Tosi wrote:
> well, the py- prefix seems wrong as well (and not part of the recommendation)
>
> On Sun, Apr 16, 2017 at 5:44 AM, Ondrej Novy <novy@ondrej.org> wrote:
> > Hi,
> >
> >
> > 2017-04-14 20:25 GMT+02:00 Sandro Tosi <morph@debian.org>:
> > > why the cli tools are in a separate packages, instead of being inside
> > > the py3k package (as it seems to suggest it uses the python3
> > > module to work)?
> >
> >
> > because it's one of our team recommendation:
> > https://wiki.debian.org/Python/LibraryStyleGuide#Executables_and_library_packages
> >
> > But section of py-cpuinfo binary package is wrong.
> >
> > --
> > Best regards
> >  Ondřej Nový
> >
> > Email: novy@ondrej.org
> > PGP: 3D98 3C52 EB85 980C 46A5  6090 3573 1255 9D1E 064B