Raymond Hettinger <raymond.hettin...@gmail.com> added the comment:
Something in the release build process is triggering this behavior (perhaps
PGO).
I observe the bug on the python.org official 3.8b3 release, official 3.7
release, but not in the official 3.6 release:
$ python3.8 ~/time_compare.py
Python ('v3.8.0b3:4336222407', 'Jul 29 2019 09:46:03') Clang 6.0
(clang-600.0.57)
CPU Time: 14.632004 Wall Clock: 7.318585415 Distance: 750
$ python3.7 ~/time_compare.py
Python ('v3.7.4:e09359112e', 'Jul 8 2019 14:54:52') Clang 6.0 (clang-600.0.57)
CPU Time: 16.405296 Wall Clock: 8.208222215000001 Distance: 750
$ python3.6 ~/time_compare.py
Python ('v3.6.8:3c6b436a57', 'Dec 24 2018 02:04:31') GCC 4.2.1 Compatible Apple
LLVM 6.0 (clang-600.0.57)
CPU Time: 8.645299 Wall Clock: 8.647321333999571 Distance: 7
However, when I do my own fresh build for 3.8b3, the problem disappears:
$ py ~/time_compare.py
Python ('tags/v3.8.0b3:4336222407', 'Aug 24 2019 23:08:57') Clang 10.0.1
(clang-1001.0.46.4)
CPU Time: 7.446087 Wall Clock: 7.447327639 Distance: 750
I build with the following process:
make distclean
./configure --with-openssl=$(brew --prefix openssl)
make
----------
nosy: +rhettinger
_______________________________________
Python tracker <rep...@bugs.python.org>
<https://bugs.python.org/issue36205>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
