[issue7459] Magic word incorrect in Python 3

Benjamin Peterson added the comment: Fixed in r76731. Thanks. -- resolution: -> fixed status: open -> closed ___ Python tracker ___ _

[issue7459] Magic word incorrect in Python 3

Changes by Benjamin Peterson : -- assignee: -> benjamin.peterson ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue7459] Magic word incorrect in Python 3

Changes by Antoine Pitrou : -- nosy: +benjamin.peterson ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://m

[issue7459] Magic word incorrect in Python 3

Antoine Pitrou added the comment: I think the point is more of self-documentation not being deceiving. Here someone tries to use import.c 's embedded documentation about existing magic numbers and he/she gets mystified because the actual magic number doesn't seem to correspond. Also, it's true

[issue7459] Magic word incorrect in Python 3

Guido van Rossum added the comment: I don't see a bug here. The value returned by imp.get_magic() matches the first bytes of a bytecode file. That's all that matters. Of course, we could remove the global variable and just use the defined constant; but that's just an optimization, not a bugfi

[issue7459] Magic word incorrect in Python 3

Changes by Arfrever Frehtes Taifersar Arahesis : Added file: http://bugs.python.org/file15499/python-3.1-fix_documentation_of_magic_word.patch ___ Python tracker ___

[issue7459] Magic word incorrect in Python 3

New submission from Arfrever Frehtes Taifersar Arahesis : Python/import.c defines magic word which is used in the beginning of .pyc files to verify if .pyc files have been generated by compatible version of Python. Python 2 supports undocumented -U option increases magic word by 1. Python 3 use