[pywin32-bugs] [ pywin32-Bugs-1799934 ] easy_install silently fails
OLD project page for the Python extensions for Windows
Brought to you by:
mhammond
Menu
▾
▴
[pywin32-bugs] [ pywin32-Bugs-1799934 ] easy_install silently fails
|
From: SourceForge.net <no...@so...> - 2009-02-13 22:51:28
|
Bugs item #1799934, was opened at 2007-09-21 20:29 Message generated for change (Comment added) made by zooko You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=1799934&group_id=78018 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: installation Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Zooko O'Whielacronx (zooko) Assigned to: Nobody/Anonymous (nobody) Summary: easy_install silently fails Initial Comment: 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 ---------------------------------------------------------------------- >Comment By: Zooko O'Whielacronx (zooko) Date: 2009-02-13 22:28 Message: 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. ---------------------------------------------------------------------- Comment By: Zooko O'Whielacronx (zooko) Date: 2009-01-02 18:10 Message: 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 ---------------------------------------------------------------------- Comment By: Zooko O'Whielacronx (zooko) Date: 2008-12-29 17:19 Message: Please upload pywin32 212 to http://pypi.python.org and then we can close this ticket. ---------------------------------------------------------------------- Comment By: Zooko O'Whielacronx (zooko) Date: 2008-12-03 12:07 Message: 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. ---------------------------------------------------------------------- Comment By: Hartmut Goebel (htgoebel) Date: 2008-09-04 10:29 Message: 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> ---------------------------------------------------------------------- Comment By: Zooko O'Whielacronx (zooko) Date: 2008-06-02 20:31 Message: 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 ---------------------------------------------------------------------- Comment By: Mark Hammond (mhammond) Date: 2008-05-03 01:30 Message: 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. ---------------------------------------------------------------------- Comment By: Zooko O'Whielacronx (zooko) Date: 2008-05-03 00:56 Message: 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. ---------------------------------------------------------------------- Comment By: Mark Hammond (mhammond) Date: 2008-05-03 00:39 Message: 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 :) ---------------------------------------------------------------------- Comment By: Zooko O'Whielacronx (zooko) Date: 2008-05-02 17:48 Message: 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. ---------------------------------------------------------------------- Comment By: SourceForge Robot (sf-robot) Date: 2008-04-23 02:20 Message: 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). ---------------------------------------------------------------------- Comment By: Mark Hammond (mhammond) Date: 2008-04-08 21:20 Message: 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. ---------------------------------------------------------------------- Comment By: Zooko O'Whielacronx (zooko) Date: 2008-01-25 14:17 Message: Logged In: YES user_id=52562 Originator: YES See also: http://mail.python.org/pipermail/distutils-sig/2007-July/007823.html ---------------------------------------------------------------------- Comment By: Mark Hammond (mhammond) Date: 2007-09-30 23:33 Message: 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. ---------------------------------------------------------------------- Comment By: Zooko O'Whielacronx (zooko) Date: 2007-09-30 22:57 Message: 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? ---------------------------------------------------------------------- Comment By: Mark Hammond (mhammond) Date: 2007-09-21 23:57 Message: 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. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=1799934&group_id=78018 |
