Bug 1629982

Summary: Python can sometimes create incorrect .pyc files
Product: Red Hat Enterprise Linux 7 Reporter: Paulo Andrade <pandrade>
Component: pythonAssignee: Victor Stinner <vstinner>
Status: CLOSED ERRATA QA Contact: Lukáš Zachar <lzachar>
Severity: medium Docs Contact:
Priority: medium    
Version: 7.3CC: hhorak, jamills, jkejda, luis.fernandez.alvarez, pviktori, python-maint, qe-baseos-apps, vstinner
Target Milestone: rc   
Target Release: 7.7   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: python-2.7.5-77.el7 Doc Type: Bug Fix
Doc Text:
Sometimes, on I/O error, Python created corrupted .pyc file (with empty code objects). The fix now checks for I/O error on reading source file (.py) to avoid produce corrupted .pyc file.
Story Points: ---
Clone Of: 1629978 Environment:
Last Closed: 2019-08-06 12:33:13 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1629978    
Bug Blocks: 1630906, 1661173    

Comment 2 Petr Viktorin (pviktori) 2018-09-26 12:48:30 UTC
As in Bug #1629978, while I'm sure the upstream patch is an improvement, I haven't checked if it addresses all instances of the underlying issue.

Comment 3 Petr Viktorin (pviktori) 2018-10-22 09:19:06 UTC
*** Bug 1629978 has been marked as a duplicate of this bug. ***

Comment 4 Victor Stinner 2018-11-19 10:09:48 UTC
I created https://src.osci.redhat.com/rpms/python/pull-request/1

Comment 5 Victor Stinner 2018-11-21 13:56:18 UTC
The fix doesn't add a new test. It's hard to reproduce the bug: it requires to get an I/O error on one specific C function. I suggest to only run sanity checks.

Comment 10 errata-xmlrpc 2019-08-06 12:33:13 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2019:2030