The python bindings as a whole are not broken, so you can't fix them. This is a
good example of a bad commit summary ;)
The o -> O change is fine of course, it's just unrelated to the object check
change so should be in a commit of its own. As for the object check change,
it's probably ok, but if we do it for ts it should be done for all similar
macros in our codebase, otherwise it'll just make things inconsistent.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/pull/1600#issuecomment-809227881
_______________________________________________
Rpm-maint mailing list
Rpm-maint@lists.rpm.org
http://lists.rpm.org/mailman/listinfo/rpm-maint
