Questions, questions ...
These new guidelines seem to be fine for pure Python packages, but I'm
maintaining a couple of packages where Python bindings are built as
subpackages of existing C libraries:
https://src.fedoraproject.org/rpms/libnbd
https://src.fedoraproject.org/rpms/libguestfs
[Yes there are good reasons for this. No we are not going to decouple
them and package the Python stuff separately.]
Running %pyproject_install etc is not really an option for us.
However I guess some of these macros could make sense
(%pyproject_save_files? %pyproject_files?). Also I don't think these
projects generate the extra *.egg-info files or how to create them.
=== Not removing older guidelines ===
There's no rush; it might well take a decade.
I guess we've got a while ...
While I've got your attention, one other package is interesting:
https://src.fedoraproject.org/rpms/nbdkit
This has Python 3 bindings but they work in completely the opposite
way to normal bindings, namely a Python interpreter is embedded in a
C program. As far as I know none of the Python guidelines in Fedora
address this scenario directly, and indeed we don't currently use any
of the special %python* macros.
Rich.
--
Richard Jones, Virtualization Group, Red Hat
http://people.redhat.com/~rjones
Read my programming and virtualization blog:
http://rwmj.wordpress.com
virt-df lists disk usage of guests without needing to install any
software inside the virtual machine. Supports Linux and Windows.
http://people.redhat.com/~rjones/virt-df/