Changes in version 0.8.0:
metadata_version as 2.1, 2.2, or 2.3.canonical_name added to get the normalized nameor.as_rfc822() no longer modifies the metadata objectproject.license instead of project.readmeflit-corePlease login to add feedback.
This update has been submitted for testing by jjames.
This update's test gating status has been changed to 'ignored'.
This update has been pushed to testing.
Just a heads-up that this update caused
python-meson-pythonto FTBFS in Rawhide, although I was able to patch it easily.I plan to backport that patch to F40 to accommodate this update.
Oh my, it seems that python-pyproject-metadata has grown more consumers than I knew about. Sorry about that. I was under the impression that version 0.8.0 contained only bug fixes. Since it appears to contain backwards incompatible changes, I'm leaning toward withdrawing this update. What do you think?
That’s probably the safer choice, unless there’s some reason to really want the update in F40. It might be OK to proceed if a more thorough impact check shows nothing else is broken.
I’ve backported the
python-meson-pythonpatch either way.python-pdm-backend, python-sphinx-theme-builder, and spglib seem okay without modification. On the other hand, python-llama-cpp-python is broken. I don't understand that, though, since when I do a mock build, python-pyproject-metadata isn't even installed. I'll have to investigate further.
I am going to withdraw this update.
This update has been unpushed.