[issue29586] Cannot run pip in fresh install of py 3.5.3

Adrian Chan added the comment: Ah, I'd forgotten about that. When I first tried to run python I got an error complaining about a missing api-ms-win-crt-runtime-l1-1.0.dll I installed the necessary VC redistributable and it solved that problem. So that's why I could successfully ensurepip

[issue29586] Cannot run pip in fresh install of py 3.5.3

Adrian Chan added the comment: Install logs attached. First set from initial install, second set from repair. -- Added file: http://bugs.python.org/file46645/py_install_logs.tar.gz ___ Python tracker <rep...@bugs.python.org> <http://bugs.p

[issue29586] Cannot run pip in fresh install of py 3.5.3

Adrian Chan added the comment: It's all working fine now, thanks. If one of the installer/windows guys wants to dig more into why this didn't install properly I'm happy to run things in my environment as necessary. -- ___ Python tracker <

[issue29586] Cannot run pip in fresh install of py 3.5.3

Adrian Chan added the comment: 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

[issue29586] Cannot run pip in fresh install of py 3.5.3

Adrian Chan added the comment: There is no traceback, that is the entirety of the output of the command. Python bin is C:\Python\Python35-32\python.exe PYTHONHOME is not set. PYTHONPATH is C:\python27\lib\site-packages\ I don't know why PYTHONPATH was set. I cleared it but it made

[issue29586] Cannot run pip in fresh install of py 3.5.3

New submission from Adrian Chan: I uninstalled python 2.7 and 3.4, then performed a fresh install of 3.5.3. Running pip with `python -m pip` as per https://docs.python.org/3.5/installing gives the following error: C:\Python\Python35-32\python.exe: No module named pip.__main__; 'pip

[issue24780] difflib.ndiff produces unreadable output when input missing trailing newline

Adrian Chan added the comment: I've attached a potential fix for this issue. While trying to fix this, I noticed that I coudn't assume that I just need to ensure that each line has a newline. If I always ensure each line in diffline has a newline, then the fourth test

[issue24780] unittest assertEqual difference output foiled by newlines

Adrian Chan added the comment: Is this still being worked on? I have a potential fix for this. -- nosy: +adchanw ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/i