For the next FESCo meeting to review: 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. We will provide a way to opt-out of it and adjust the guidelines to prefer explicit bytecompilation of such files. Later, the old behavior will be opt-in only or will cease to exist. Note that bytecompilation in Python-specific directories (e.g. /usr/lib/python3.6/) is not affected.
+1
Seems like a straightforward +1 to me.
AGREED: F29 Self Contained Change: No more automagic Python bytecompilation is accepted (+7, 0, 0)
Metadata Update from @zbyszek: - Issue untagged with: meeting - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.