Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.python > #98947 > unrolled thread

Re: Mapping between python packages and distro packages?

Started byChris Angelico <rosuav@gmail.com>
First post2015-11-18 17:44 +1100
Last post2015-11-18 17:44 +1100
Articles 1 — 1 participant

Back to article view | Back to comp.lang.python

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  Re: Mapping between python packages and distro packages? Chris Angelico <rosuav@gmail.com> - 2015-11-18 17:44 +1100

#98947 — Re: Mapping between python packages and distro packages?

FromChris Angelico <rosuav@gmail.com>
Date2015-11-18 17:44 +1100
SubjectRe: Mapping between python packages and distro packages?
Message-ID<mailman.404.1447829099.16136.python-list@python.org>
On Wed, Nov 18, 2015 at 3:33 PM, Ben Finney <ben+python@benfinney.id.au> wrote:
> What would count as “the right package”?
>
> Do you mean “the package that has that PyPI distribution URL in its
> ‘debian/watch’ configuration”?
>
> Do you mean “the package that names that PyPI distribution in its
> ‘debian/copyright’ “Source” field”?
>
> Or something else?

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

[toc] | [standalone]


Back to top | Article view | comp.lang.python


csiph-web