From 5a6e940f03fb497d5a529b83ae4a35ddb2416814 Mon Sep 17 00:00:00 2001 From: Petr Bokoc Date: Oct 25 2018 13:47:45 +0000 Subject: [PATCH 1/2] 125 - No more automagic Python bytecompilation --- diff --git a/modules/release-notes/pages/developers/Development_Python.adoc b/modules/release-notes/pages/developers/Development_Python.adoc index 9a2ac8c..aa11f36 100644 --- a/modules/release-notes/pages/developers/Development_Python.adoc +++ b/modules/release-notes/pages/developers/Development_Python.adoc @@ -3,3 +3,11 @@ include::{partialsdir}/entities.adoc[] [[sect-python]] = Python + +== No more automagic Python bytecompilation + +The current way of automatic *Python* byte-compiling of files outside Python-specific directories is too magical and error-prone. It is built on heuristics that are increasingly wrong. This change provides a way to opt out of it, and adjusts the guidelines to prefer explicit bytecompilation of such files. Later, the old behavior will either become opt-in only, or cease to exist. + +Note that bytecompilation in Python-specific directories (e.g. [filename]`/usr/lib/python3.6/`) is not affected. + +See the link:++https://fedoraproject.org/wiki/Changes/No_more_automagic_Python_bytecompilation++[Fedora Wiki change page] for detailed documentation. From 49e8e2bc454c2819f2bb08ffab89afeb540aa21a Mon Sep 17 00:00:00 2001 From: Petr Bokoc Date: Oct 25 2018 13:48:41 +0000 Subject: [PATCH 2/2] Fix formatting in Python --- diff --git a/modules/release-notes/pages/developers/Development_Python.adoc b/modules/release-notes/pages/developers/Development_Python.adoc index aa11f36..492b2a7 100644 --- a/modules/release-notes/pages/developers/Development_Python.adoc +++ b/modules/release-notes/pages/developers/Development_Python.adoc @@ -6,7 +6,10 @@ include::{partialsdir}/entities.adoc[] == No more automagic Python bytecompilation -The current way of automatic *Python* byte-compiling of files outside Python-specific directories is too magical and error-prone. It is built on heuristics that are increasingly wrong. This change provides a way to opt out of it, and adjusts the guidelines to prefer explicit bytecompilation of such files. Later, the old behavior will either become opt-in only, or cease to exist. +The current way of automatic *Python* byte-compiling of files outside Python-specific directories is too magical and error-prone. +It is built on heuristics that are increasingly wrong. +This change provides a way to opt out of it, and adjusts the guidelines to prefer explicit bytecompilation of such files. +Later, the old behavior will either become opt-in only, or cease to exist. Note that bytecompilation in Python-specific directories (e.g. [filename]`/usr/lib/python3.6/`) is not affected.