> NAK, the name disable_automagic_pybytecompile strongly indicates that it
> disables it *completely* but it does something entirely different.
Well, it disables the automagic part. If you get better name, suggest one.
> If byte-compilation outside python libdirs is too magic and error-prone, I
> think it's better to just drop it from the build root policy unconditionally,
> and let packagers call the script manually from spec if needed. There are too
> many magic variables already and replacing one magic with another...
Works for me. However that break all the things. The idea was to keep to old
cruft working while /usr/bin/python is Python 2, provide and opt out for now.
Convert all python 3 things to use the opt out, adjust the guidelines and don't
let new stuff use the old way.
Once /usr/bin/python is no longer Python 2, kill this with fire.
--
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-383891017
_______________________________________________
Rpm-maint mailing list
Rpm-maint@lists.rpm.org
http://lists.rpm.org/mailman/listinfo/rpm-maint
