*so what is my hopefully sinple solution anyway? i do n't see myself anytime soon getting off of Build 10074 of Win 10. i don't have pip in the Scripts folder where I was told it should be. I was thinking of doing a complete disinstall/reinstall of Python 3.4 to see if that helps. *
*On Fri, Sep 4, 2015 at 4:50 PM, eryksun <eryk...@gmail.com <eryk...@gmail.com>> wrote:* > > > > > > > > > > > > > > > > > > *On Fri, Sep 4, 2015 at 11:35 AM, Steve Burrus <steveburru...@gmail.com > <steveburru...@gmail.com>> wrote: > > "C:\Users\SteveB>py -m pip > Job > information querying failed You're using build 10074, an old build of > Windows 10 that had a buggy Job object API. This was fixed in build 10159: > http://bugs.python.org/issue24127 <http://bugs.python.org/issue24127> FYI, > the py launcher runs Python in a job that's configured to kill Python if > the the launcher gets killed. This is necessary if py.exe is started by a > console shell such as cmd.exe or powershell.exe. The shell waits on py.exe, > not python.exe. If the job didn't kill python.exe, then Python would > compete with the shell for console input. *
-- https://mail.python.org/mailman/listinfo/python-list
