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: [snip] Python 3.0a5: 3130 (lexical exception stacking, including POP_EXCEPT) [snip] Python 3.1a0: 3150 (optimize conditional branches: introduce POP_JUMP_IF_FALSE and POP_JUMP_IF_TRUE) [snip] Note that the value has 1 added to it in py3k's _PyImport_Init, giving: python 3.0: magic=3131 = 0x0c3b (hex) = 0x3b 0x0c 0xc0 0xd0a (header) and python 3.1: magic=3151 = 0x0c4f (hex) = 0x4f 0x0c 0x0d 0x0a (header)
> python 3.0: magic=3131 = 0x0c3b (hex) = 0x3b 0x0c 0xc0 0xd0a (header) should read: > python 3.0: magic=3131 = 0x0c3b (hex) = 0x3b 0x0c 0xc0 0x0a (header)
I've sent the patch to the upstream mailing list (file.com), but it's current stuck in the moderator queue as I'm not yet subscribed (they seem to require human intervention for approving subscriptions)
hello Dave, thanks for the patch, added in file-5.03-11.fc13 I am subscribed to the list, so if your post doesn't show up there I can send the patch from my address.
...now I see your mail in the upstream mailing list
(In reply to comment #4) > ...now I see your mail in the upstream mailing list http://mx.gw.com/pipermail/file/2009/000483.html