https://bugzilla.redhat.com/show_bug.cgi?id=2497737
--- Comment #6 from Cristian Le <[email protected]> --- It is a fragile design and I do insist to open a ticket with upstream to properly support a PEP517 build system. Here is an example: - core.* imports foo - in python 3.72 a new std library core is introduced and foo picks up a dependency on it - either foo starts to import the package's core.* or package is importing the std core.* The proper pythonic packaging approach is for each package to own a namespace and use that in their imports. The project should be pip/uv installable and be consumed like that, not having a custom build process. This not a strictly blocking issue, but as packagers we ought to give feedback to upstream about following proper packaging guidelines and (not even that) modern practices. -- You are receiving this mail because: You are always notified about changes to this product and component You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2497737 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-spam&short_desc=Report%20of%20Bug%202497737%23c6 -- _______________________________________________ package-review mailing list -- [email protected] To unsubscribe send an email to [email protected] Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/[email protected] Do not reply to spam, report it: https://forge.fedoraproject.org/infra/tickets/issues/new
