Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.python > #102078 > unrolled thread

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

Back to article view | Back to comp.lang.python

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Re: 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." <apetrie@aspetrie.net> - 2016-01-23 14:43 -0500
    Re: pip install mitmproxy - fails on watchdog-0.8.3.tar.gz with "Permission denied" error (Python 2.7.11 on Win XP SP3); Larry Hudson <orgnut@yahoo.com> - 2016-01-24 14:35 -0800
      Re: pip install mitmproxy - fails on watchdog-0.8.3.tar.gz with "Permission denied" error (Python 2.7.11 on Win XP SP3); Terry Reedy <tjreedy@udel.edu> - 2016-01-24 20:27 -0500
      Re: pip install mitmproxy - fails on watchdog-0.8.3.tar.gz with "Permission denied" error (Python 2.7.11 on Win XP SP3); eryk sun <eryksun@gmail.com> - 2016-01-26 15:30 -0600

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

Chris,

Thanks for your response -- much appreciated.

Please see my remarks embedded below.

----- Original Message ----- 
From: "Chris Angelico" <rosuav@gmail.com>
To: "Steve Petrie, P.Eng." <apetrie@aspetrie.net>
Cc: <python-list@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@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.

[toc] | [next] | [standalone]

#102084

On 01/23/2016 11:43 AM, Steve Petrie, P.Eng. wrote:
[snip]
>> 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 :)
>
A minor clarification...

If the path string is typed directly into Windows where it is parsed by (whatever is the current 
equivalent of) command.com, forward slashes are NOT accepted.  Because there it is used to 
indicate command-line options.

But if this string comes from a program where it is parsed by an API, it IS accepted.  And this 
has been the case even since MSDOS prior to Windows.

      -=- Larry -=-

[toc] | [prev] | [next] | [standalone]

#102085

On 1/24/2016 5:35 PM, Larry Hudson via Python-list wrote:

> If the path string is typed directly into Windows where it is parsed by
> (whatever is the current equivalent of) command.com, forward slashes are
> NOT accepted.

More specifically, / is not accepted in paths to be executed. It seems 
to be generally accepted in path arguments, as in cd path, or

C:\Users\Terry>C:\programs\python35\python.exe C:/programs/python34/tem.py

-- 
Terry Jan Reedy

[toc] | [prev] | [next] | [standalone]

#102138

 On Sun, Jan 24, 2016 at 7:27 PM, Terry Reedy <tjreedy@udel.edu> wrote:
>
> More specifically, / is not accepted in paths to be executed. It seems to be
> generally accepted in path arguments, as in cd path, or
>
> C:\Users\Terry>C:\programs\python35\python.exe C:/programs/python34/tem.py

An exception that comes to mind is takeown.exe, which fails to parse
paths that use slash as the value for /F.

A couple of exceptional cases in the Windows API come to mind. The
"\\?\" extended path syntax requires backslash. Also referencing named
kernel objects requires a backslash after either the "Global" prefix
or a private namespace prefix. For example, in "Global/ObjectName" the
slash is just another character in the name, so the object manager
doesn't follow the "Global" symbolic link to \BaseNamedObjects but
instead creates"Global/ObjectName" in the session's named objects
directory.

[toc] | [prev] | [standalone]

Back to top | Article view | comp.lang.python

csiph-web