easy_install silently fails

[ghost]

If I install pywin32 by executing pywin32-210.win32-py2.5.exe , it works.

If I run "easy_install pywin32" then it claims that it is downloading and installing pywin32-210.win32-py2.5.exe , and after a while it claims that it has successfully installed it, but an attempt to use pywin32 yields errors like this:

$ python -c 'import win32process'
Traceback (most recent call last):
File "<string>", line 1, in <module>
ImportError: DLL load failed: The specified module could not be found.

I'm not sure whether this should be considered a bug in pywin32 or in easy_install, or both.

Regards,

Zooko

Reported by: zooko

Original Ticket: "pywin32/bugs/334":https://sourceforge.net/p/pywin32/bugs/334

[ghost]

Logged In: YES
user_id=14198
Originator: NO

After install, pywin32_postinstall.py needs to be run, but ezsetup apparently does not provide a facility to do that. You may like to ask them for such a facility.

Original comment by: mhammond

[ghost]

Logged In: YES
user_id=52562
Originator: YES

I will see if I can make the pywin32_postinstall.py stuff get done automatically upon easy_install.

In the meantime, is there some way to make this failure loud instead of silent? How do you tell easy_install: yes, there is a package in the expected format (.zip) in the expected place (pypi), but it isn't actually going to work?

Original comment by: zooko

[ghost]

Logged In: YES
user_id=14198
Originator: NO

I've no idea - that too is an easy_install question. I've never used easy_install to install pywin32, and I've never recommended anyone else do it either.

Original comment by: mhammond

[ghost]

Logged In: YES
user_id=52562
Originator: YES

See also:

http://mail.python.org/pipermail/distutils-sig/2007-July/007823.html

Original comment by: zooko

[ghost]

Logged In: YES
user_id=14198
Originator: NO

I believe PJE recently fixed a bug in setuptools that was causing problems with pywin32 as an egg. Please try again after build 211 is released.

Original comment by: mhammond

[ghost]

• status: open --> pending

Original comment by: mhammond

[ghost]

• status: pending --> closed

Original comment by: sf-robot

[ghost]

Logged In: YES
user_id=1312539
Originator: NO

This Tracker item was closed automatically by the system. It was
previously set to a Pending status, and the original submitter
did not respond within 14 days (the time period specified by
the administrator of this Tracker).

Original comment by: sf-robot

[ghost]

• status: closed --> pending

Original comment by: zooko

[ghost]

Logged In: YES
user_id=52562
Originator: YES

Hi, I went to test this so I could definitely close this bug, but it turns out that pywin32 build 211 isn't downloadable yet.

Original comment by: zooko

[ghost]

Logged In: YES
user_id=14198
Originator: NO

Try starship.python.net/crew/mhammond/pywin32-210.9.win32-py2.5.exe. Note I'm not sure of the status of the bug I referred to - ie, I'm not sure if a released version of setuptools has the bug fixed (but I assume you are ontop of that :)

Original comment by: mhammond

[ghost]

• status: pending --> open

Original comment by: zooko

[ghost]

Logged In: YES
user_id=52562
Originator: YES

Well, I'm afraid that starship.python.net/crew/mhammond/pywin32-210.9.win32-py2.5.exe doesn't work with the current setuptools -- setuptools v0.6 final. Could you tell me how to build pywin32 packages from CVS so I can experiment? Thanks.

Original comment by: zooko

[ghost]

Logged In: YES
user_id=14198
Originator: NO

That installer is quite recent - you may need to get the latest setuptools rather than the latest pywin32. Either way, just grab the CVS sources, install the Vista SDK, and execute "setup.py" - to get some basic instructions printed.

Original comment by: mhammond

[ghost]

Logged In: YES
user_id=52562
Originator: YES

This is the ticket on the setuptools issue tracker to track the progress of fixing this in setuptools:

http://bugs.python.org/setuptools/issue18

Original comment by: zooko

[ghost]

Logged In: YES
user_id=376953
Originator: NO

There are actually two problems:

1) pywin32_postinstall.py can not be run manually when using eggs since it does not use pkg_resources.

This is fixed by patch 2092722
<http://sourceforge.net/tracker/index.php?func=detail&aid=2092722&group\_id=78018&atid=551956>.

2) easy_install does not run pywin32_postinstall.py. It looks like there is no mechanism to do this.

This problem has been filed at <http://bugs.python.org/setuptools/issue18>

Original comment by: htgoebel

[ghost]

Okay I just tested pywin32 212 with the latest trunk of setuptools (0.6c10dev), and it worked! However, the pywin32 package is not linked from http://pypi.python.org/simple/pywin32 , so easy_install doesn't know how to download it. Please put a link on http://pypi.python.org/simple/pywin32 pointing to the 212 binaries and this ticket is done.

Original comment by: zooko

[ghost]

Please upload pywin32 212 to http://pypi.python.org and then we can close this ticket.

Original comment by: zooko

[ghost]

Having pywin32 hosted somewhere that easy_install will discover is needed for the imminent release of tahoe-lafs v1.3.0. However, if the current release of pywin32 is not hosted on pypi, we can instead upload a copy of the pywin32 package to a tahoe grid. :-)

http://allmydata.org/trac/tahoe/ticket/566 # host tahoe dependencies on a tahoe grid

Original comment by: zooko

[ghost]

Well, I think I was wrong when I said that pywin32 212 can be easy_install'ed. Probably I accidentally already had pywin32 installed when I tested it. I just tested it again and it doesn't work -- ImportError win32api.

Original comment by: zooko

[ghost]

Hey good news! I used distribute v0.6.3 from http://pypi.python.org/pypi/distribute and gave it this URL: http://downloads.sourceforge.net/project/pywin32/pywin32/Build%20214/pywin32-214.win32-py2.6.exe?use\_mirror=softlayer and it worked!

Here is the command line that I executed:

easy_install -v "http://downloads.sourceforge.net/project/pywin32/pywin32/Build%20214/pywin32-214.win32-py2.6.exe?use\_mirror=softlayer"

so, if only pywin32 were hosted on pypi or if a direct link to the .exe's were registered in the metadata which is hosted on pypi then a simple 'easy_install pywin32' would work, and so would automatic installation of pywin32 when
installing projects which specify that they depend on pywin32 in their setup.py.

So please upload the pywin32 binaries to pypi, or else configure the metadata to point to some URL (I'm afraid I'm not sure which one) which will let easy_install find the binaries on sf.net.

Original comment by: zooko

[Avasam]

Easy Install (and eggs) have been deprecated in favor of wheels and package managers like pip https://setuptools.pypa.io/en/latest/deprecated/easy_install.html
Kindof relates to #2208

[Avasam]

xref: twisted/twisted#3004