#334 easy_install silently fails

open
nobody
5
2008-05-03
2007-09-21
No

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

Discussion

  • Mark Hammond

    Mark Hammond - 2007-09-21

    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.

     
  • Zooko O'Whielacronx

    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?

     
  • Mark Hammond

    Mark Hammond - 2007-09-30

    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.

     
  • Mark Hammond

    Mark Hammond - 2008-04-08
    • status: open --> pending
     
  • Mark Hammond

    Mark Hammond - 2008-04-08

    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.

     
  • SourceForge Robot

    • status: pending --> closed
     
  • SourceForge Robot

    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).

     
  • Zooko O'Whielacronx

    • status: closed --> pending
     
  • Zooko O'Whielacronx

    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.

     
  • Mark Hammond

    Mark Hammond - 2008-05-03

    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 :)

     
  • Zooko O'Whielacronx

    • status: pending --> open
     
  • Zooko O'Whielacronx

    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.

     
  • Mark Hammond

    Mark Hammond - 2008-05-03

    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.

     
  • Zooko O'Whielacronx

    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

     
  • Hartmut Goebel

    Hartmut Goebel - 2008-09-04

    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>

     
  • Zooko O'Whielacronx

    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.

     
  • Zooko O'Whielacronx

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

     
  • Zooko O'Whielacronx

    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

     
  • Zooko O'Whielacronx

    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.

     
  • Zooko O'Whielacronx

    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.

     

Log in to post a comment.