Re: "py-" prefix shouldn't be needed for Python-based ports that are programs, not libraries
- Reply: Charlie Li : "Re: "py-" prefix shouldn't be needed for Python-based ports that are programs, not libraries"
- Reply: Jamie Landeg-Jones : "Re: "py-" prefix shouldn't be needed for Python-based ports that are programs, not libraries"
- In reply to: Charlie Li : "Re: "py-" prefix shouldn't be needed for Python-based ports that are programs, not libraries"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Fri, 16 Feb 2024 07:02:27 UTC
On 2/15/24 22:48, Charlie Li wrote: > This distinction does not practically exist; any Python package, even > if primarily a program, can be specified and imported as a library in > another as a dependency. See meson, which had to grow flavours when > meson-python came about. This isn't true. If the program has one main function and several helper application-specific submodules - none of them can be used by any other software as dependency because everything is application-specific. If the package has the description "Command line utility to xx" - this likely means that this is just a command line application and nothing more, and it shouldn't have the "py-" prefix. Yuri