Path: csiph.com!fu-berlin.de!uni-berlin.de!not-for-mail From: Chris Angelico Newsgroups: comp.lang.python 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); Date: Sun, 24 Jan 2016 06:56:56 +1100 Lines: 28 Message-ID: References: <5B9D2FB5D87C47E78205CE5B96110CCC@Dell> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 X-Trace: news.uni-berlin.de tmdY0vPDBaG42ZIHG7xudg6Tpa7EhFl8JPe+SlMocjbw== Return-Path: X-Original-To: python-list@python.org Delivered-To: python-list@mail.python.org X-Spam-Status: OK 0.003 X-Spam-Evidence: '*H*': 0.99; '*S*': 0.00; 'subject:Python': 0.05; 'cc:addr:python-list': 0.09; 'docs.': 0.09; 'bug': 0.10; 'jan': 0.11; 'subject:error': 0.11; 'systems.': 0.11; 'output': 0.13; 'file,': 0.15; 'properly': 0.15; '(via': 0.16; '2016': 0.16; '24,': 0.16; 'from:addr:rosuav': 0.16; 'from:name:chris angelico': 0.16; 'pathname': 0.16; 'quotes)': 0.16; 'received:io': 0.16; 'received:psf.io': 0.16; 'subject:Permission': 0.16; 'subject:fails': 0.16; 'subject:install': 0.16; 'wrote:': 0.16; 'steve': 0.18; 'windows': 0.20; 'cc:2**0': 0.20; 'cc:addr:python.org': 0.20; 'to:2**1': 0.21; 'am,': 0.23; "haven't": 0.24; 'header:In-Reply-To:1': 0.24; 'message- id:@mail.gmail.com': 0.27; 'issues.': 0.29; 'spaces': 0.29; 'raise': 0.29; "i'd": 0.31; 'fixed': 0.31; 'changed': 0.33; 'file': 0.34; 'running': 0.34; 'list': 0.34; 'received:google.com': 0.35; 'but': 0.36; 'should': 0.36; 'received:209.85': 0.36; 'subject:" ': 0.36; 'subject:: ': 0.37; 'expect': 0.37; 'say': 0.37; 'received:209.85.213': 0.37; 'things': 0.38; 'manual': 0.38; 'received:209': 0.38; 'names': 0.38; 'anything': 0.38; 'mailing': 0.38; 'from:': 0.39; 'subject:-': 0.39; 'rather': 0.39; 'subject:with': 0.40; "you'll": 0.61; 'matter': 0.63; 'p.s.': 0.65; 'soon': 0.65; 'bang': 0.84; 'chrisa': 0.84; 'studying': 0.84; 'upstream': 0.84; 'assured': 0.95 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=1AJBPuNnRsXq+0eIjU8CDjubs0Ldvl+or7Tpd+3fEhQ=; b=kCLiQEFOJwG1o/pjdH4SNsseBH1Wac3u2D3ke+Iw5z4geeHBY3Jlff8gapGIauYt1n PlAErYmhgWyKUBs/qfOWCefnEh2cv/RrXCqzYYCpPyE+dcaqV3bTfDsLfpmMDbhqxdHv VMjoTtOgrz43zl2OGxbz8uyH39qfnqgt7Z2lT8XhX8z33ls0NHtKZeDecHxQw04dA0o5 YC1f/DbzhuiEAL/3r65uNjMAbf2JQEtIhryy/Hz9usmkea6PTdXf+SKk71pqVlkj9r7Z yjW53cbLUdAuf2w5NQbv5CavMs306A9UE58og4fR7GMSDUbxty6Fo0vJd48DGbcuIE04 yGPQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=1AJBPuNnRsXq+0eIjU8CDjubs0Ldvl+or7Tpd+3fEhQ=; b=fVt3Ml3Teo9UVs7MEk5EwmsehV+QOIkLaVhbEqUOE/nQA5mlj44+vY9ESuVx04wzQH r6Vm96CWOUGU52PvetRlGLhjHxPC6T54mJ6BBB5y6+VVvAJLg2lIdJsxPMyiiluD5Ssv daBeU92VCtqb6tZRhxEnK+Gqt2untK0RxZUqSwj5SlhFsLN7OSTA4nH27NiZlII8xhU6 TQQq3KNE1iJCf3U/w6jPql0EaZkSzjy6Q8vkDBh/4BH78rsff5Ym+eB5bQP+CZsJmqr+ 7X3t/PiHT3g9f1O/M0J9C3BHQgbH9ErUBOz9tIiprWfgwcZZBvhIrXgn6hPLAK6JjJtB KRUQ== X-Gm-Message-State: AG10YOQJtrN0D+iUloGuYFZPCiGBSz7J8DSbAW5Xke1/E0hWPt0MvecN/vqhcDwbPpFWCZ6Vkr6ZZoI9wWwdZQ== X-Received: by 10.50.28.19 with SMTP id x19mr10182829igg.92.1453579016433; Sat, 23 Jan 2016 11:56:56 -0800 (PST) In-Reply-To: <5B9D2FB5D87C47E78205CE5B96110CCC@Dell> X-BeenThere: python-list@python.org X-Mailman-Version: 2.1.20+ Precedence: list List-Id: General discussion list for the Python programming language List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Xref: csiph.com comp.lang.python:102056 On Sun, Jan 24, 2016 at 6:43 AM, Steve Petrie, P.Eng. wrote: > In case other Windows XP "orphans" want to use mitmdump, here's what I > learned (via Google): > > 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" Spaces in names are often a pain. I'd raise this upstream as a bug report - it should be fixed properly rather than depending on manual editing. > 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. I'd say you'll do best with a mailing list dedicated to mitmdump; what you're looking at now is application-specific issues. > P.S. Be assured -- I will soon be moving away from Windows XP to a new > computer running Debian Linux. Good plan! That's what I use on all my systems. So many things are easier when you move off XP. ChrisA