Blair Hall wrote:
> >
> >
> > I get your point that the first manifest I provided is not specific to
> > the DLL, but the second (embedded in the DLL) manifest that I posted
> > seems to identify a particular version of msvcr90.dll. Sadly, Windows
> > does not worry about matching the version of ms
Blair Hall wrote:
>
>
> I get your point that the first manifest I provided is not specific to
> the DLL, but the second (embedded in the DLL) manifest that I posted
> seems to identify a particular version of msvcr90.dll. Sadly, Windows
> does not worry about matching the version of msvcr90.dll: i
> I have used py2exe on another project that creates an EXE. This
> > project also imports uuid (it basically imports the same stuff I am
> > using now, but for a different application). In that case, the
> > manifest seems to work as expected. So, I wonder what is different in
> > the case of my D
Blair Hall wrote:
>
>
>
> One ugly alternative would be to edit sys.path in your code before you
> start your imports. If you remove everything but the Windows
> directories, that should solve the problem.
>
>
> I don't follow. Surely sys.path has nothing to do with it? It is the
> Loa
> You might consider double-checking your message subjects before
> responding. That's especially important when you read the digest.
>
Oh dear, I am sorry. I hadn't twigged to how that worked. I have restored
the original subject now, from my initial post. Hope that helps.
> Blair Hall wrote:
This appears to be due to way rpcrt4.dll is loaded by ctypes. If a
side-by-side assembly has already loaded a version that’s not
compatible with the activation context of Python itself, ctypes will attempt to
use it anyway.
Roger
"Blair Hall" wrote in message
news:CAJeTVArsN8Vp_e6cnF3yU
I have just tried this same project on a computer with Win7-64 Professional
and MS Office 2010 (but with the same 2.7.8 32-bit Python installation).
The error does NOT occur.
So, is it the difference between Win7 for Home users and professional, or
is it something to do with MS Office (the bug oc
Hi!
I test with my own Python-COM-server (Ponx), and I have also an error:
-
Microsoft Visual C++ Runtime Library
---
Runtime Error!
Program: D:\Dev\Python\PonxTest101.exe
R6034
An applicat
OK, sorry, here are some more details.
I have Python 2.7.8, win32, running on a Windows7 64-bit home machine (not
professional).
Here is my python script:
#---
import pythoncom
#import uuid
class Bug:
_reg_clsid_ = '{E3D5F332-F080-47B3-A319-A3A0E287E466
Which version of Python are you running?
32 or 64 bit?
Which version of pywin32?
Which version of Windows?
Can you make a small test case that will demonstrate the error?
On Thu, Oct 16, 2014 at 7:47 PM, Blair Hall wrote:
> I have a small python COM server that worked fine with Excel until I
>
I have a small python COM server that worked fine with Excel until I
decided to import the standard Python 'uuid' module.
Now I get the Windows Runtime error R6034 "An application has made an
attempt to load the C runtime library incorrectly"
I there anything that I can do to fix this?
__
11 matches
Mail list logo
