On Fri, 15 Jun 2018, Jason L Tibbitts III wrote:
As part of a recent guideline change (https://pagure.io/packaging-committee/issue/772) which ties in with an accepted F29 change (https://fedoraproject.org/wiki/Changes/No_more_automagic_Python_bytecompilation), this section of the guidelines was overhauled for F29+: https://fedoraproject.org/wiki/Packaging:Python_Appendix#Manual_byte_compilation The quick summary is that Fedora will be changing to not automatically byte-compile python files which are installed outside of the usual python library locations. Currently implemented is the %_python_bytecompile_extra macro which allows packages to disable this byte-compilation of "extra" python files. The default is still to compile these files, so technically nothing changes. In order to prepare for the default to change in a future release, the packaging guidelines have changed to require packages which install .py files outside of the regular python library locations to do the following: * Set %_python_bytecompile_extra to 0 to disable the automatic compilation of the extra python files. * Manually byte-compile those files which do actually need to be compiled. This is done with the %py_byte_compile macro, which as a bonus requires that you specify which python version will be used for the compilation.
In a couple of my packages, the python files you are detecting are documentation or sample code. Do we care in that case? In fact, maybe it's best those aren't byte-compiled?
Scott _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx/message/I5MOFJGBUUR67CLWTONEOJUK7FJPACD6/
