En Thu, 03 Sep 2009 02:16:13 -0300, David Lees
escribió:
In case anyone else has this problem, my mistake was a PYTHONPATH that
pointed to my Python 2.5 installation. I simply changed it to:
C:\Python26\Lib\site-packages
and reran the Pywin32 installer and all is fine.
Assuming you insta
David Lees wrote:
I install Python 2.6.2 with no problem, but then run the installer for
pywin32 from Source Forge and get this message at the end. IDLE works,
but Pywin32 does not.
Traceback (most recent call last):
File "", line 601, in
File "", line 313, in install
ImportError: DLL lo
I install Python 2.6.2 with no problem, but then run the installer for
pywin32 from Source Forge and get this message at the end. IDLE works,
but Pywin32 does not.
Traceback (most recent call last):
File "", line 601, in
File "", line 313, in install
ImportError: DLL load failed: The spec
On Thu, 14 May 2009 08:33:12 +1000, Mark Hammond
wrote:
> But if PYTHONPATH was set incorrectly it really doesn't matter how
> Python was installed, it would still fail. The installer didn't set
> PYTHONPATH, a human did.
Hi Mark,
Well I am just trying to write a package manager for python b
On 13/05/2009 2:18 PM, David Lyon wrote:
On Wed, 13 May 2009 05:32:16 +0200, "Martin v. Löwis"
wrote:
I think this was a case of obscure misconfiguration of the system.
It is always possible to configure a system in such a way that even
the most resilient installation procedure will break.
Te
On Wed, 13 May 2009 13:54:49 +0200, Thomas Heller
>
> Well, if you don't like the windows installer than you can always
> install from the sources. Please go ahead and try it out.
Thanks for the offer...
but aren't python .eggs supposed to remove the need for doing that ?
Regards
David
--
David Lyon schrieb:
> On Wed, 13 May 2009 05:32:16 +0200, "Martin v. Löwis"
> wrote:
>
>> I think this was a case of obscure misconfiguration of the system.
>> It is always possible to configure a system in such a way that even
>> the most resilient installation procedure will break.
>
> Techni
On Wed, 13 May 2009 05:32:16 +0200, "Martin v. Löwis"
wrote:
> I think this was a case of obscure misconfiguration of the system.
> It is always possible to configure a system in such a way that even
> the most resilient installation procedure will break.
Technically, you are right..
but imho.
> lol - so simple...
>
> Thankfully, we got a quick answer by the package writing master himself..
>
> but imho - package installation shouldn't be that tricky.. it should be
> click and shoot... which is what i'm working on doing..
>
> I have to say that I don't mind being corrected because I
> Thanks for the help. I just got it to install for Python 2.6. All I did
> was change PYTHONPATH (as suggested by Mark) from
> C:\Python25\Lib\site-packages to C:\Python26\Lib\site-packages
Why do you have PYTHONPATH set at all?
--
http://mail.python.org/mailman/listinfo/python-list
On Tue, 12 May 2009 23:57:48 GMT, David Lees
> Mark and David,
>
> Thanks for the help. I just got it to install for Python 2.6. All I
> did was change PYTHONPATH (as suggested by Mark) from
> C:\Python25\Lib\site-packages to C:\Python26\Lib\site-packages
lol - so simple...
Thankfully, we g
Mark Hammond wrote:
Probably some import statement is finding a .pyd module built against
Python 2.5 instead of Python 2.6; it might be that PYTHONPATH points
somewhere wrong, or the registry for Python 2.6 is setup wrong, or
something else entirely...
Cheers,
Mark
On 12/05/2009 3:13 PM, Da
Probably some import statement is finding a .pyd module built against
Python 2.5 instead of Python 2.6; it might be that PYTHONPATH points
somewhere wrong, or the registry for Python 2.6 is setup wrong, or
something else entirely...
Cheers,
Mark
On 12/05/2009 3:13 PM, David Lyon wrote:
Hi,
Hi,
hmmm... that's annoying..
Whilst I don't have an exact answer I have a few hunches...
Perphaps what has happened is that the windows installer between
the versions of pywin32 has installed newer versions of the same
dlls over the top of older ones.
Or, possibly, the installer hasn't wanted
Hi,
hmmm... that's annoying..
Whilst I don't have an exact answer I have a few hunches...
Perphaps what has happened is that the windows installer between
the versions of pywin32 has installed newer versions of the same
dlls over the top of older ones.
Or, possibly, the installer hasn't wanted
On Tue, 12 May 2009 02:22:56 GMT, David Lees
wrote:
> I have no problem installing Python 2.6.2 for windows under XP SP3 and
> IDLE and the command line versions work fine. When I run the pywin32
> installer downloaded from sourceforge (pywin32-212.win32-py2.6.exe) I
> get the following error
I have no problem installing Python 2.6.2 for windows under XP SP3 and
IDLE and the command line versions work fine. When I run the pywin32
installer downloaded from sourceforge (pywin32-212.win32-py2.6.exe) I
get the following error message:
Traceback (most recent call last):
File "", line
17 matches
Mail list logo
