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 Adrian Chan
Recipients Adrian Chan, docs@python, eryksun, paul.moore, steve.dower, tim.golden, zach.ware
Date 2017-02-17.13:20:56
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1487337657.28.0.69321751787.issue29586@psf.upfronthosting.co.za>
In-reply-to
Content
Thanks, but I know how to drive a terminal ;)

Your hunch was basically correct though.  I ran again with `python -v -m pip` (see with_pip_dir.txt), and see that python is attempting to import pip from my user directory (C:\Users\amc2\pip).  This is an empty directory, except for an old pip log file from 2.7.

If I rename the directory to something unrelated, `python -m pip` just fails with:

C:\Python\Python35-32\python.exe: No module named pip.

So mystery 1 is solved.

I've definitely selected the pip option in the python installer.  I also repaired the installation, with the pip option selected, and the error still remains.
Where is pip supposed to be located on a win7 install?
History
Date User Action Args
2017-02-17 13:20:57Adrian Chansetrecipients: + Adrian Chan, paul.moore, tim.golden, docs@python, zach.ware, eryksun, steve.dower
2017-02-17 13:20:57Adrian Chansetmessageid: <1487337657.28.0.69321751787.issue29586@psf.upfronthosting.co.za>
2017-02-17 13:20:57Adrian Chanlinkissue29586 messages
2017-02-17 13:20:56Adrian Chancreate