Red Hat Bugzilla – Bug 1271636
RFE: add detection of Python bytecode for recent versions of Python
Last modified: 2016-11-04 03:36:21 EDT
Also happens for
(versions of Python >3.2)
+++ This bug was initially created as a clone of Bug #809898 +++
Can we ensure that "file" in RHEL6 identifies Python bytecode for all released versions of Python?
(i.e. 2.7, 3.0, 3.1, 3.2, and, later this year, 3.3)
I'm not sure if the Fedora work below made it into RHEL6:
+++ This bug was initially created as a clone of Bug #531082 +++
Created attachment 366152 [details]
Add bytecode values for Python 3.0 and 3.1
Description of problem:
Attached is a patch that adds support for Python 3.0 and Python 3.1 bytecode files to the .pyc/.pyo support.
With this file:
$ file /usr/lib/python3.1/re.pyo
/usr/lib/python3.1/re.pyo: python 3.1 byte-compiled
Caveat: only tested with 3.1; I calculated up the value for 3.0 from the source in python's py3k branch's Python/import.c:
Python 3.0a5: 3130 (lexical exception stacking, including POP_EXCEPT)
Python 3.1a0: 3150 (optimize conditional branches:
introduce POP_JUMP_IF_FALSE and POP_JUMP_IF_TRUE)
Note that the value has 1 added to it in py3k's _PyImport_Init,
python 3.0: magic=3131 = 0x0c3b (hex) = 0x3b 0x0c 0xc0 0xd0a (header)
python 3.1: magic=3151 = 0x0c4f (hex) = 0x4f 0x0c 0x0d 0x0a (header)
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.