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


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

Re: Python27.dll could not be found

Started byGisle Vanem <gvanem@yahoo.no>
First post2015-03-02 20:22 +0100
Last post2015-03-02 20:22 +0100
Articles 1 — 1 participant

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: Python27.dll could not be found Gisle Vanem <gvanem@yahoo.no> - 2015-03-02 20:22 +0100

#86779 — Re: Python27.dll could not be found

FromGisle Vanem <gvanem@yahoo.no>
Date2015-03-02 20:22 +0100
SubjectRe: Python27.dll could not be found
Message-ID<mailman.62.1425324241.13471.python-list@python.org>
Dave Angel wrote:

> When I ran Windows, I had written a simple utility that searched the PATH for a specified file.
> I called it which.bat to match the Linux equivalent.

I've written a similar tool; envtool --path --python python27.dll

Matches in %PATH:
       15 May 2013 - 21:43:38: f:\ProgramFiler\Python27\python27.dll
Matches in Python's sys.path[]:
       15 May 2013 - 21:43:38: f:\programfiler\Python27\python27.dll

(available at http://watt-32.net/misc/#envtool )

> You can look to see where the system thinks the Python executable is located by doing
>
>      ftype .py
> and seeing what it shows.  Mine shows Python.File
>
>    Then do
>      assoc  Python.File
>
> to see an actual path.

That will give you the path of python.exe. Not pythonXX.dll (as the
OP had problems with).

But by Windows DLL loading rules, it's IMHO safer to have pythonXX.dll
in the directory of python[w].exe. On Windows, ACAICR the Python MSI
installer puts pythonXX.dll in %Windir\system32. So it depends on how
the OP installed his Python.


-- 
--gv

[toc] | [standalone]


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


csiph-web