Steve Dower added the comment: Looks like I acknowledged the error in the patch and then didn't fix it when I applied it.
The change needed here is what Mark describes above, plus recompiling the executable stubs. Or alternatively, I can probably just edit out the bytes in the existing stub for 3.6.0 and fix it properly for 3.6.1. Ned - thoughts? This regressed from 3.4 and has not worked properly for both architectures (simultaneously) since 3.5. ---------- keywords: +3.4regression nosy: +larry, ned.deily priority: normal -> release blocker resolution: fixed -> status: closed -> open versions: +Python 3.7 _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue26071> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
