#772 Manual Python byte compilation change
Closed: accepted Opened by churchyard.

Original

https://fedoraproject.org/wiki/Packaging:Python_Appendix#Manual_byte_compilation

Draft

https://fedoraproject.org/wiki/User:Churchyard/Manual_byte_compilation

Diff

https://fedoraproject.org/w/index.php?title=User%3AChurchyard%2FManual_byte_compilation&type=revision&diff=520122&oldid=520118

Explanation

Explained in https://fedoraproject.org/wiki/Changes/No_more_automagic_Python_bytecompilation


Example change in package https://src.fedoraproject.org/rpms/python-uranium/pull-request/1#request_diff

We discussed this ticket at this weeks meeting (https://meetbot-raw.fedoraproject.org/fedora-meeting-1/2018-06-07/fpc.2018-06-07-16.00.txt):

  • x772 Manual Python byte compilation change (geppetto, 16:06:58)
  • LINK:
    https://fedoraproject.org/wiki/Changes/Move_usr_bin_python_into_separate_package
    (mhroncok, 16:15:10)
  • ACTION: Manual Python byte compilation change (+1:5, 0:0, -1:0)
    (geppetto, 16:35:19)

Metadata Update from @james:
- Issue untagged with: meeting
- Issue tagged with: writeup

Metadata Update from @james:
- Issue assigned to tibbs

Announcement text:

The section of the Python packaging appendix relating to manual byte compilation has been amended with a new section applying to Fedora 29 and newer only. Because this is a rarely-trafficked section of the guidelines and the change mandates modifications to a number of packages, I will summarize here:

If your package installs files with names ending in ".py" outside of the standard directories for python files (/usr/lib(64)?/python\d.\d) then in rawhide you must disable automatic byte compilation of files outside of these directories by adding "%global _python_bytecompile_extra 0" to your spec and then, if necessary, manually byte-compile those files with a specific python version using the %py_byte_compile macro.

There are on the order of 500 packages which will need attention to fix this before the default value of %_python_bytecompile_extra becomes 0 (and potentially breaks many of those packages) in a future release. Lists of these packages will be posted separately on the devel list.

Metadata Update from @tibbs:
- Issue untagged with: hasdraft, writeup
- Issue tagged with: announce

Metadata Update from @tibbs:
- Issue untagged with: announce
- Issue close_status updated to: accepted
- Issue status updated to: Closed (was: Open)

Metadata