kivy / kivy / 27978273122 / 2

60%

master: 60%

push

github

Modernize build: PEP 621 metadata (#9325)

* Modernize build: PEP 621 metadata, gate Kivy-Garden on mobile, split examples wheel

- Migrate project metadata, dependencies and extras from setup.py/setup.cfg
  into a PEP 621 [project] table in pyproject.toml; slim setup.py to the
  C-extension build only (version stays dynamic).
- Gate the Kivy-Garden tool out of iOS/Android wheels via a
  `sys_platform != "ios" and sys_platform != "android"` marker; it cannot run
  on mobile. Other deps stay unconditional.
- Split the Kivy-examples wheel into packaging/kivy_examples/ with its own
  pyproject.toml + setup.py; repoint the osx/manylinux/windows CI builds to it
  and drop the KIVY_BUILD_EXAMPLES path from setup.py.
- Retire setup.cfg: move [coverage:run] -> [tool.coverage.run] and
  [kivy] -> [tool.kivy]; update cython_cfg.py and doc conf.py to read
  [tool.kivy] from pyproject.toml (tomllib with tomli fallback).

* fix: use relative ext_modules paths for PEP 517/660 editable builds

Under isolated PEP 517/660 builds, __file__ resolves to an absolute path,
making src_path and all derived extension source/depends paths absolute.
setuptools' wheel/editable-wheel builder rejects absolute paths in setup()
arguments, aborting the Windows editable install. Convert the source and
depends paths to be relative to the setup.py directory before passing them
to CythonExtension.

* build: make Kivy-Garden an unconditional dependency

The sys_platform != ios/android marker did not achieve its goal: mobile
build pipelines (kivy-ios, python-for-android) resolve dependencies on a
desktop build host, where PEP 508 markers evaluate against the host, not
the target. The gate was therefore a no-op for excluding kivy-garden from
mobile builds. Mobile trimming is handled where it actually works, via the
consumer's exclude list (e.g. kivy-ios [tool.kivy.ios].exclude).

3247 of 6493 branches covered (50.01%)

28870 of 48543 relevant lines covered (59.47%)

0.59 hits per line