Path: csiph.com!usenet.pasdenom.info!weretis.net!feeder4.news.weretis.net!eternal-september.org!feeder.eternal-september.org!mx02.eternal-september.org!.POSTED!not-for-mail From: ElChino Newsgroups: comp.lang.python Subject: Re: Python launcher problem Date: Fri, 31 Jul 2015 18:30:52 +0200 Organization: A noiseless patient Spider Lines: 46 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Injection-Date: Fri, 31 Jul 2015 16:29:12 +0000 (UTC) Injection-Info: mx02.eternal-september.org; posting-host="fd24a31e26909c9856abe0079e8aba83"; logging-data="1337"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1+7KlIIA/o2iSExUiGY29+5" User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:36.0) Gecko/20100101 Firefox/36.0 SeaMonkey/2.33.1 In-Reply-To: Cancel-Lock: sha1:0Au3QLGDEXk0w5/0d9HB/U6+69k= Xref: csiph.com comp.lang.python:94815 Zachary Ware wrote: > On Jul 30, 2015 2:05 AM, "ElChino" > wrote: > > > > If I in a cmd-shell (actually it is 4NT), do: > > c:>py -3 -V & python3 -V > > > > I get: > > Requested Python version (3) not installed << ! from py -3 -V > > Python 3.5.0b2 << ! from the 2nd cmd. > > > > What nonsense is this? I DO HAVE Python3 in my %PATH. > > A Registry setting gone haywire? > > Did you perchance rename the installed 'python.exe' to 'python3.exe'? > That would be enough to break the launcher. If you want a 'python3' > command, you can copy 'python.exe' to 'python3.exe', but 'python.exe' > needs to remain where it was. That's what I did: ls -l f:/ProgramFiler/Python35/python*.exe -rwxr-xr-x 1 XX Administratorer 37664 May 31 04:18 f:/ProgramFiler/Python35/python.exe -rwxr-xr-x 1 XX Administratorer 37664 May 31 04:18 f:/ProgramFiler/Python35/python3.exe -rwxr-xr-x 1 XX Administratorer 37664 May 31 04:18 f:/ProgramFiler/Python35/pythonw.exe They all depends on: f:\ProgramFiler\Python35\python35.dll The one and only python35.dll on this box. And also on PATH. I took Ben Finney's advice to heart. From: http://code.activestate.com/lists/python-list/684547/ Calling ‘python’ is now ambiguous, and with Python 2 slipping inexorably into the past, increasingly the ‘python’ command is the wrong choice for code that we want to survive in the future. I am seeing a growing call, with which I agree, to recommend explicitly calling ‘python2’ or ‘python3’ as commands. That's why I made that copy; even if some of you find that strange on Windows. I'll investigate is there's an issue with the Registry later.