Sworddragon added the comment: > Is this issue just for 2.7? 3.3 was selected as the affected version, but > the error message text seems limited to 2.7
You have given me a good hint. My script is running on python3 with the shbang line "#!/usr/bin/python3 -OOtt". But it makes a subcall to python (which defaults to python2.7) instead of python3. This explains why I couldn't even reproduce this with a simple script. ---------- resolution: -> invalid status: open -> closed _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue16625> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
