Re: Mapping between python packages and distro packages?

From	Laura Creighton <lac@openend.se>
Newsgroups	comp.lang.python
Subject	Re: Mapping between python packages and distro packages?
Date	2015-11-18 20:30 +0100
Message-ID	<mailman.422.1447875051.16136.python-list@python.org> (permalink)
References	<20151118032903.GA8040@sg1> <85vb90c4fv.fsf@benfinney.id.au> <CAPTjJmotkP4LPy90TBKSvC5b6ugptY4+5wkRxMp1ZvcqK3S=cQ@mail.gmail.com>

Show all headers | View raw

In a message of Wed, 18 Nov 2015 17:44:51 +1100, Chris Angelico writes:

>I don't know how the program would detect it, but I'd be thinking "the
>one where 'sudo apt-get install PACKAGENAME' gets the same code that
>'pip install THING' gets". In a lot of cases, PACKAGENAME will simply
>be python-THING or python3-THING, eg python3-sqlalchemy,
>python3-scipy, python3-bs4; as a human, that's what I'd try first. But
>having a program recognize this would be hugely beneficial.
>
>ChrisA

The problem is that this may not exist.  Debian developers, when faced
with a python package, may decide to break it up into several pieces,
and make several debian packagages.  If you want the same functionality
you have to load all of the debian packages, which of course involves
finding out what they are.

apt-cache search <PyPi name> works reasonably well, as long as you are
willing to put up with some false hits.  And it assumes you have a debian
system handy, of course.

Laura

Back to comp.lang.python | Previous | Next | Find similar | Unroll thread

Thread

Re: Mapping between python packages and distro packages? Laura Creighton <lac@openend.se> - 2015-11-18 20:30 +0100

csiph-web