Martin v. Löwis wrote:
>> That's odd. In theory, having msvcr90.dll in C:\Python26 should be
>> sufficient, as once python.exe is loaded, its directory is added to
>> the DLL search path. Maybe it's something to do with the "side by side
>> manifest installation" stuff (or whatever it's called).
>
> That shouldn't be hard - I'll set up a Windows virtual machine with no
> additional software on it and can use that for testing. If you want me
> to try anything out, let me know and I can do so in a guaranteed clean
> environment.
I think I've a spare license of XP Home around somewhere. I'm g
> That shouldn't be hard - I'll set up a Windows virtual machine with no
> additional software on it and can use that for testing. If you want me
> to try anything out, let me know and I can do so in a guaranteed clean
> environment.
That should be a reasonable setup. Try moving the manifest files
On 18/03/2008, "Martin v. Löwis" <[EMAIL PROTECTED]> wrote:
> > Martin, can you comment? It looks like the 3.0 installer uses 2 copies
> > of msvcr90.dll, where the 2.6 one doesn't. I would have thought that
> > only one is necessary, but Gregor's experiments seem to demonstrate
> > otherwise.
>
>
> We are still having problems to integrate the MS Merge module into our
> MSI. Martin is working on the problem. In the mean time you can work
> around the problem by installing the MSVCRT 9.0 Redist.
While this is a work-around for the people trying to run the alpha
releases, it effectively pr
> That's odd. In theory, having msvcr90.dll in C:\Python26 should be
> sufficient, as once python.exe is loaded, its directory is added to
> the DLL search path. Maybe it's something to do with the "side by side
> manifest installation" stuff (or whatever it's called).
Yes, with VS 2008, the DLL s
Paul Moore schrieb:
> That's odd. In theory, having msvcr90.dll in C:\Python26 should be
> sufficient, as once python.exe is loaded, its directory is added to
> the DLL search path. Maybe it's something to do with the "side by side
> manifest installation" stuff (or whatever it's called).
>
> Mart
On 17/03/2008, Gregor Lingl <[EMAIL PROTECTED]> wrote:
> > Another thought - do you have any copies of msvcr90.dll on your PATH?
> > I don't think it'll make a difference, but if you do can you try
> > renaming them?
> >
> >
> No I don't! Only in c:\Python26, in c:\Python30 and on c:\Python30\DLLs.
Paul Moore schrieb:
> On 17/03/2008, Gregor Lingl <[EMAIL PROTECTED]> wrote:
>> When doing the same call to execute idle as you, I got the following:
>>
>> Traceback (most recent call last):
>> File "c:\Python26\Lib\idlelib\idle.py", line 6, in
>> import PyShell
>> File "c:\Python26\Li
On 17/03/2008, Gregor Lingl <[EMAIL PROTECTED]> wrote:
> When doing the same call to execute idle as you, I got the following:
>
> Traceback (most recent call last):
> File "c:\Python26\Lib\idlelib\idle.py", line 6, in
> import PyShell
> File "c:\Python26\Lib\idlelib\PyShell.py", line 9,
Hi Paul,
thanks for you efforts, but up to now it still didn't work.
I'm using Windows XP Professional (32 bit).
I tried an install on two different machines with the same negative result.
I proceeded like you suggested.
- I installed for all users,
- I disabled the register extensions
When doi
11 matches
Mail list logo
