(after perusing the Fedora RFE explaining the change)

The failure example given has a confusion in the extension *.py (which can also 
apparently is the country code for Paraguay).

Why not just add an additional test for an executable bit on a *.py file 
instead of attempting detection of within tree compilation? That certainly 
solves the example failure case, no fuss, no muss, without all these quite 
mystifying macro enablers and disablers and python2 vs python3 and in-tree vs 
out-of-tree caveats.

-- 
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/434#issuecomment-383919301
_______________________________________________
Rpm-maint mailing list
Rpm-maint@lists.rpm.org
http://lists.rpm.org/mailman/listinfo/rpm-maint

Reply via email to