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:
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: it
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 DLL? Well
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
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 blairdh...@gmail.com wrote in message
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 blairdh...@gmail.com wrote:
I have a small python COM server that worked fine
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?
