> The idea is that "libraries" (or "modules") start with python-, while
> "applications" do not emphasize the language they are written in. Calibre,
> for instance, also is not called python-calibre.

In this case it seems there are quite a few packages that go against
this convention. 'python-pip', for example, is mostly used as a CLI
*application*.

This has been actually causing me confusion. At some point I was
wondering how I should call a package I was writing and it seems I
erroneously added "python-" taking example from other packages :/

Wojtek

-- (sig_start)
website: https://koszko.org/koszko.html
fingerprint: E972 7060 E3C5 637C 8A4F  4B42 4BC5 221C 5A79 FD1A
follow me on Fediverse: https://friendica.me/profile/koszko/profile

♥ R29kIGlzIHRoZXJlIGFuZCBsb3ZlcyBtZQ== | ÷ c2luIHNlcGFyYXRlZCBtZSBmcm9tIEhpbQ==
✝ YnV0IEplc3VzIGRpZWQgdG8gc2F2ZSBtZQ== | ? U2hhbGwgSSBiZWNvbWUgSGlzIGZyaWVuZD8=
-- (sig_end)


On Thu, 27 Jul 2023 08:56:32 +0200 Andreas Enge <andreas@enge.fr> wrote:

> Am Wed, Jul 26, 2023 at 09:25:43PM -0700 schrieb Andy Tai:
> > curious poetry is not named python-poetry in Guix as following
> > convention of most python packages  
> 
> See here:
>    https://guix.gnu.org/de/manual/devel/en/html_node/Python-Modules.html
> 
> The idea is that "libraries" (or "modules") start with python-, while
> "applications" do not emphasize the language they are written in. Calibre,
> for instance, also is not called python-calibre.
> 
> Of course with script languages there is no clear technical barrier;
> but a package with lots of binaries will not start with python-, while
> software that is mainly used in lines "import xyz;" tends to be called
> python-something.
> 
> Andreas
> 
>