-
Notifications
You must be signed in to change notification settings - Fork 419
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Include dist-info for python3-dnf #1997
Include dist-info for python3-dnf #1997
Conversation
Looks OK to me, I'd just modify the commit message which is saying "Include dist-info for python3-libdnf5". |
And what about other packages like |
This is the DNF 4 cousin to this patch [0] for DNF 5. Per [1], Python packages should include some minimal distribution metadata, e.g. to make the package appear in `pip list`. Perhaps the "proper way" to generate this dist-info metadata would be to write a pyproject.toml and use a conventional Python build system like Poetry to build `python3-dnf` rather than doing it with CMake, but this is a way to do it with minimal changes to the build process. Closes RhBug:2239323 [2] [0] rpm-software-management/dnf5#447 [1] https://packaging.python.org/en/latest/specifications/core-metadata/#core-metadata, [2] https://bugzilla.redhat.com/show_bug.cgi?id=2239323 = changelog = msg: Add metadata for `dnf` Python package type: bugfix resolves: https://bugzilla.redhat.com/show_bug.cgi?id=2239323
7184349
to
fcd93f4
Compare
Whoops thanks!
Sure, I'll PR libdnf. I don't know whether it'd be worth adding metadata to each python3-dnf-plugin. |
This is the libdnf version of this patch [0] for DNF 4. Per [1], Python packages should include some minimal distribution metadata, e.g. to make the package appear in `pip list`. [0] rpm-software-management/dnf#1997 [1] https://packaging.python.org/en/latest/specifications/core-metadata/#core-metadata = changelog = msg: Add metadata for `libdnf` Python package type: bugfix
This is the libdnf version of this patch [0] for DNF 4. Per [1], Python packages should include some minimal distribution metadata, e.g. to make the package appear in `pip list`. [0] rpm-software-management/dnf#1997 [1] https://packaging.python.org/en/latest/specifications/core-metadata/#core-metadata = changelog = msg: Add metadata for `libdnf` Python package type: bugfix
This is the libdnf version of this patch [0] for DNF 4. Per [1], Python packages should include some minimal distribution metadata, e.g. to make the package appear in `pip list`. [0] rpm-software-management/dnf#1997 [1] https://packaging.python.org/en/latest/specifications/core-metadata/#core-metadata = changelog = msg: Add metadata for `libdnf` Python package type: bugfix
This is the DNF 4 cousin to this patch [0] for DNF 5.
Per [1], Python packages should include some minimal distribution metadata, e.g. to make the package appear in
pip list
.Perhaps the "proper way" to generate this dist-info metadata would be to write a pyproject.toml and use a conventional Python build system like Poetry to build
python3-dnf
rather than doing it with CMake, but this is a way to do it with minimal changes to the build process.Closes RhBug:2239323 [2]
[0] rpm-software-management/dnf5#447
[1] https://packaging.python.org/en/latest/specifications/core-metadata/#core-metadata,
[2] https://bugzilla.redhat.com/show_bug.cgi?id=2239323
= changelog =
msg: Add metadata for
dnf
Python packagetype: bugfix
resolves: https://bugzilla.redhat.com/show_bug.cgi?id=2239323