Bug 10842 - python package must not set PYTHONDONTWRITEBYTECODE
Summary: python package must not set PYTHONDONTWRITEBYTECODE
Status: RESOLVED DUPLICATE of bug 3348
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: High normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL: http://svnweb.mageia.org/packages/cau...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-07-26 10:09 CEST by Hartmut Goebel
Modified: 2013-07-26 10:44 CEST (History)
1 user (show)

See Also:
Source RPM: python-2.7.3-7.mga3.src.rpm
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Hartmut Goebel 2013-07-26 10:09:19 CEST 
The python RPM contains scripts for profile.d which forcefully sets PYTHONDONTWRITEBYTECODE. Setting this variable leds to a lot of trouble, see bug 3348, bug 3358, and bug 3350. And it leads to a regression in bug 3358#c33.

Pythons default behavior is to write byte-code, so setting this variable changes the normal behavior and objects user expectations. If someone really wants to disable writing byte-code, he should set this variable actively.

Solution:

Just remove (or comment) the two lines containing PYTHONDONTWRITEBYTECODE from the .spec file.


Reproducible: 

Steps to Reproduce:
Hartmut Goebel 2013-07-26 10:10:46 CEST

Keywords: (none) => Junior_job
Priority: Normal => High
Blocks: (none) => 3358, 3348

Comment 1 Philippe Makowski 2013-07-26 10:31:08 CEST 
No way to fix that in Mageia 2 and Mageia 3
It will be fix in Mageia 4, not before
and it is a duplicate of #3348

*** This bug has been marked as a duplicate of bug 3348 ***

Status: NEW => RESOLVED
CC: (none) => makowski.mageia
Resolution: (none) => DUPLICATE

Philippe Makowski 2013-07-26 10:31:34 CEST

Keywords: Junior_job => (none)
Blocks: 3348, 3358 => (none)

Comment 2 Hartmut Goebel 2013-07-26 10:36:51 CEST 
Reopening, as this bug is explicitly for Cauldron. And it is not a duplicate of 3348, but a precondition for solving 3348:

If we remove PYTHONDONTWRITEBYTECODE from all .spec-files, but still have it in the profile.d-files, byte-code will still not be written when building packages.

Status: RESOLVED => REOPENED
Resolution: DUPLICATE => (none)

Comment 3 Philippe Makowski 2013-07-26 10:44:25 CEST 
Please stop, and really trust me, it is a duplicate
bug 3348 is not about "remove PYTHONDONTWRITEBYTECODE from all .spec-files"
but change profile.d files

and at the same time, we need to remove PYTHONDONTWRITEBYTECODE from some spec files

*** This bug has been marked as a duplicate of bug 3348 ***

Status: REOPENED => RESOLVED
Resolution: (none) => DUPLICATE
Note You need to log in before you can comment on or make changes to this bug.