https://bugzilla.redhat.com/show_bug.cgi?id=1739786 Ankur Sinha (FranciscoD) <sanjay.ankur@xxxxxxxxx> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(pkopkan@xxxxxxxxx | |m) | --- Comment #10 from Ankur Sinha (FranciscoD) <sanjay.ankur@xxxxxxxxx> --- (In reply to Petr Viktorin from comment #9) > > There's also no mention of these macros in the python packaging guidelines---should we wait for them to be made public before using them? > > They are currently experimental. If you use them, you should be prepared to > follow the development and maybe adjust the package if we need to do any > changes (though we'll try to not break stuff). > In this case, I think it is best to wait until they're announced to the whole community---as part of the Python packaging guidelines---before using them. What do you think Zbigniew? We need to ensure that these specs remain consistent since all members of the neuro-sig (at least) would be looking after them. I'm all for early adoption, but I do not think these are ready for adoption yet, especially since the review process also requires others to know how they are meant to be used. We may not mind keeping up with the changes to these macros, but it isn't fair to expect others to keep up with their development also. (Additionally, the current set of python macros already makes the spec quite short and neat, so moving to these new ones doesn't seem too urgent to me.) -- You are receiving this mail because: You are on the CC list for the bug. You are always notified about changes to this product and component _______________________________________________ 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
