曹忠 added the comment:
Thanks, I see.
Brett Cannon 于2016年10月25日 周二 00:28写道:
Brett Cannon added the comment:
Closing this as a third-party Debian issue (if it even matters as bytecode
is an optimization local to a machine and so different magic numbers
shouldn't matter).
Brett Cannon added the comment:
Closing this as a third-party Debian issue (if it even matters as bytecode is
an optimization local to a machine and so different magic numbers shouldn't
matter).
--
nosy: +brett.cannon
resolution: -> third party
status: open -> closed
Zachary Ware added the comment:
I suspect Debian 9's Python 3.5.2 has patches beyond v3.5.2, including the
patch from #27286 (34d24c51eab6).
What problem is this causing for you?
--
nosy: +doko, serhiy.storchaka, zach.ware
___
Python tracker
曹忠 added the comment:
I try, still the same:
On debian 9 and python 3.5.2:
>>> importlib.util.MAGIC_NUMBER
b'\x17\r\r\n'
On windows and python 3.5.2
>>> importlib.util.MAGIC_NUMBER
b'\x16\r\r\n'
--
___
Python tracker
Mariatta Wijaya added the comment:
Hi.
imp.get_magic() is deprecated since 3.4, see the documentation here
https://docs.python.org/3/library/imp.html?highlight=get_magic#imp.get_magic
You should use importlib.util.MAGIC_NUMBER instead.
Please try it.
Thanks.
--
nosy: +Mariatta
New submission from 曹忠:
On debian 9 and python 3.5.2:
>>> imp.get_magic()
b'\x17\r\r\n'
On windows and python 3.5.2
>>> imp.get_magic()
b'\x16\r\r\n'
the same python version, magic number is the same, why not?
--
components: Build
messages: 278830
nosy: 曹忠
priority: normal
severity: