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 terry.reedy
Recipients eryk sun, frostyelsa, paul.moore, steve.dower, terry.reedy, tim.golden, zach.ware
Date 2016-12-19.21:23:09
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1482182589.67.0.109156655677.issue29014@psf.upfronthosting.co.za>
In-reply-to
Content
Here is another possible reason (and cure) for intentionally installed  python to not work.  Just posted to Python list.

"Turns out that another instance of Python *was* installed, not as part of OEM software, but by a digital camera (Califone) that is being used in some of our classrooms.  The suggestion to look for environmental variables was the key  -  on the PCs where we were having the problem, there was a variable starting with PYTHON ... which pointed to the camera software.  Once the camera was uninstalled, Python 3.5.2 worked just fine."
History
Date User Action Args
2016-12-19 21:23:09terry.reedysetrecipients: + terry.reedy, paul.moore, tim.golden, zach.ware, steve.dower, eryk sun, frostyelsa
2016-12-19 21:23:09terry.reedysetmessageid: <1482182589.67.0.109156655677.issue29014@psf.upfronthosting.co.za>
2016-12-19 21:23:09terry.reedylinkissue29014 messages
2016-12-19 21:23:09terry.reedycreate