On 26. 01. 24 4:33, Nico Kadel-Garcia wrote:
What is the*fascination* with splitting and renaming packages this way?
No idea generally, but in the world of Python packaging, the two cases I know (poetry, flit) were motivated by folks not wanting to pull in full-blown package and environment management apps when they only want to pip install something that uses it.
The split made a lot of sense.
core - PEP517 backend https://peps.python.org/pep-0517/ the rest - an app that let's you "manage" your project
Scenario:
- The developer uses the full app to create and develop the project. - The user uses -core to build and install it.
(Obviously a developer is free to just use -core as well, if they like it. Many upstream projects use flit-core only.)