➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author yan12125
Recipients Peter Ebden, benjamin.peterson, pablogsal, rhettinger, serhiy.storchaka, yan12125
Date 2019-07-13.13:52:33
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1563025954.08.0.153083318748.issue34722@roundup.psfhosted.org>
In-reply-to
Content 
I encounter another case that leads to non-deterministic bytecode. For example, with commit e6b46aafad3427463d6264a68824df4797e682f1 + PR 9472, I got:

$ cat foobar.py
_m = None
$ PYTHONHASHSEED=0 ./python -m compileall --invalidation-mode=unchecked-hash foobar.py
Compiling 'foobar.py'...
$ sha256sum __pycache__/foobar.cpython-39.pyc
7f84b08d5536390d6ce4ccb2d65e259449c56549ee9cc67560f61771824f20ea  __pycache__/foobar.cpython-39.pyc
$ rm __pycache__/foobar.cpython-39.pyc
$ PYTHONHASHSEED=1 ./python -m compileall --invalidation-mode=unchecked-hash foobar.py
Compiling 'foobar.py'...
$ sha256sum __pycache__/foobar.cpython-39.pyc
46dadbb92ad6e1e5b5f8abe9f107086cd231b2b80c15fe84f86e2081a6b8c428  __pycache__/foobar.cpython-39.pyc

In this case there are no sets. I guess the cause is different. Should I open a new issue?
History
Date User Action Args
2019-07-13 13:52:34yan12125setrecipients: + yan12125, rhettinger, benjamin.peterson, serhiy.storchaka, Peter Ebden, pablogsal
2019-07-13 13:52:34yan12125setmessageid: <1563025954.08.0.153083318748.issue34722@roundup.psfhosted.org>
2019-07-13 13:52:34yan12125linkissue34722 messages
2019-07-13 13:52:33yan12125create