Graham Wideman added the comment: David: Yes, as it turns out you are absolutely right, in a manner of speaking. I have retested this exhaustively today, and here's the root cause.
It turns out that in testing, I must have activate a particular simplified test script by invoking only scriptname.py rather than invoking 'python scriptname.py'. (And then repeating that mistake by reinvoking via console history... doh!) The latter reliably invokes python 3.3.2, because that's the only python in my PATH. The former, it turns out, invokes the Windows Python Launcher, which finds a previously installed Python 2.7.1, despite that not being on the PATH. So, in my mind, the possibility of launching any version other than Python 3.3.2 did not enter the picture. Prior to this, I was only vaguely aware that Windows Python Launcher existed. Ironically, it was probably installed by Python 3.3.2. Sorry for the bogus bug alert. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue19136> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
