Consider a RHEL 9 spec file with does things like:

    %generate_buildrequires
    %global python3_pkgversion 3
    %pyproject_buildrequires
    %global python3_pkgversion 3.11
    %pyproject_buildrequires

    %build
    %global python3_pkgversion 3
    %pyproject_wheel
    %global python3_pkgversion 3.11
    %pyproject_wheel

    %install
    %global python3_pkgversion 3
    %pyproject_install
    %pyproject_save_files module
    %global python3_pkgversion 3.11
    %pyproject_install
    %pyproject_save_files module

This should work, but it will blow up at the install stage:

Traceback (most recent call last):
  File "/usr/lib/rpm/redhat/pyproject_save_files.py", line 775, in <module>
    main(cli_args)
  File "/usr/lib/rpm/redhat/pyproject_save_files.py", line 730, in main
    file_section, module_names = pyproject_save_files_and_modules(
                                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/rpm/redhat/pyproject_save_files.py", line 708, in pyproject_save_files_and_modules
    parsed_records = load_parsed_record(pyproject_record)
                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/rpm/redhat/pyproject_save_files.py", line 676, in load_parsed_record
    raise FileExistsError("%pyproject install has found more than one *.dist-info/RECORD file. "
FileExistsError: %pyproject install has found more than one *.dist-info/RECORD file. Currently, %pyproject_save_files supports only one wheel → one file list mapping. Feel free to open a bugzilla for pyproject-rpm-macros and describe your usecase.


Even if we manage to fix this somehow, there are 2 wheels built in pyproject-wheeldir when the Python project contains an extension module:

    $ ls -1 /var/lib/mock/centos-stream+epel-next-9-x86_64/root/builddir/build/BUILD/pyproject-wheeldir/
    reproducer_double-1-cp39-cp39-linux_x86_64.whl
    reproducer_double-1-cp311-cp311-linux_x86_64.whl

And the %pyproject_insatll macro will likely try to install them both or blow up differently.

--------------

I propose we include %{python3_pkgversion} in:

 - %{_pyproject_wheeldir}
 - %{_pyproject_builddir}
 - %{_pyproject_files_prefix}

That should isolate the entire state between different %{python3_pkgversion} values.

If we want to make this 100% backwards compatible, we could only include %{python3_pkgversion} when it is not 3.