pip install mitmproxy - fails on watchdog-0.8.3.tar.gz with "Permission denied" error (Python 2.7.11 on Win XP SP3);

[Steve Petrie, P.Eng.]

Chris,

Thanks for your response -- much appreciated.

Please see my remarks embedded below.

----- Original Message ----- 
From: "Chris Angelico" <rosuav at gmail.com>
To: "Steve Petrie, P.Eng." <apetrie at aspetrie.net>
Cc: <python-list at python.org>
Sent: Saturday, January 23, 2016 10:14 AM
Subject: Re: pip install mitmproxy - fails on watchdog-0.8.3.tar.gz with 
"Permission denied" error (Python 2.7.11 on Win XP SP3);


> On Fri, Jan 22, 2016 at 3:40 AM, Steve Petrie, P.Eng.
> <apetrie at aspetrie.net> wrote:
>> In both failure cases, it looks to me like there is a bug in the pip 
>> logic,
>> that is using a *nix forward slash "/" instead of a double backslash 
>> "\\"
>> before the file name "make.bat".
>
> I'm not sure what your exact problem is, but I can say that it isn't
> this; the Unix-style forward slash is perfectly legal under Windows
> (and it's even legal to mix and match).
>
> ChrisA

I never knew that the forward slash is legal under Windows -- thanks for 
the tip :)

After further research, I got mitmproxy installed under Windows XP. Now 
mitmdump starts ok (with one "warning").

* * *
* * *

In case other Windows XP "orphans" want to use mitmdump, here's what I 
learned (via Google):

1. There was a bug in pip-8.0.0 (bug fixed recently in pip-8.0.2) that 
caused the "Permission denied" error:

I did another upgrade of pip, and this time the upgrade installed 
pip-8.0.2 (instead of pip-8.0.0).

And pip-8.0.2 successfully installed mitmproxy.

2. But then mitmdump wouldn't start (can't use mitmproxy under 
Windows -- there's no GUI port):

   C:\Documents and Settings\SteveP>mitmdump --help
   failed to create process.

This "failed to create process" problem, was caused by whitespace, in 
the pathname to the python directory, in the bang line in file 
mitmdump-script.py:

I changed the bang line (wrapping the pathname in double quotes) in file 
mitmdump-script.py:

   from: #!e:\a p p s\python27\python.exe
      to: #!"e:\a p p s\python27\python.exe"

and now mitmdump starts ok with one warning:

   C:\Documents and Settings\SteveP>mitmdump --help
   e:\a p p 
s\python27\lib\site-packages\watchdog\observers\__init__.py:89: 
UserWarning: Failed to import read_directory_changes. Fall back to 
polling.
     warnings.warn("Failed to import read_directory_changes. Fall back 
to polling.")
   usage: mitmdump-script.py [options] [filter]
   ...

I tried to fix the warning, but so far no success (due to my Python 
ignorance).

However, mitmdump does start (with the same warning) and it creates an 
empty output file:

   C:\Documents and Settings\SteveP>mitmdump -w mitmdump_20160123.txt
   e:\a p p 
s\python27\lib\site-packages\watchdog\observers\__init__.py:89: 
UserWarning: Failed to import read_directory_changes. Fall back to 
polling.
     warnings.warn("Failed to import read_directory_changes. Fall back 
to polling.")

I haven't yet got mitmdump to actually write anything to the output 
file, but I expect that's just a matter of studying the mitmdump docs.

* * *
* * *

Thanks again for the response.

Best Regards,

Steve

P.S. Be assured -- I will soon be moving away from Windows XP to a new 
computer running Debian Linux.