https://bugzilla.redhat.com/show_bug.cgi?id=2164882 Ben Beasley <code@xxxxxxxxxxxxxxxxxx> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |fedora-review? Assignee|nobody@xxxxxxxxxxxxxxxxx |code@xxxxxxxxxxxxxxxxxx Status|NEW |ASSIGNED CC| |code@xxxxxxxxxxxxxxxxxx --- Comment #2 from Ben Beasley <code@xxxxxxxxxxxxxxxxxx> --- Preliminary requests: - Port to “new Python guidelines”: https://docs.fedoraproject.org/en-US/packaging-guidelines/Python/ - See if you can run any of the tests, or if they all need network/database servers/etc.; since the PyPI sdist lacks tests, you would need to package from a GitHub archive. It would be nice if upstream could tag the last few releases, but it seems straightforward enough to identify the commits corresponding to the PyPI releases in this case, e.g. https://github.com/vutran1710/PyrateLimiter/archive/cbdd3c6544d50319f183c86dcdaa20803cbfa878/PyrateLimiter-cbdd3c6544d50319f183c86dcdaa20803cbfa878.tar.gz is the source for 2.8.5. I’m happy to help if you run into obstacles or it’s not obvious what to do for any of these. -- 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=2164882 _______________________________________________ package-review mailing list -- package-review@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to package-review-leave@xxxxxxxxxxxxxxxxxxxxxxx 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/package-review@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
