On Thu, Aug 14, 2008 at 8:56 PM, Tim van der Leeuw <[EMAIL PROTECTED]> wrote:
> Hi,
>
> Since I haven't heard on the topic anymore and am now at home to put the
> laptop on the internet, here's the trace I currently get when from my Python
> app I try to open a standard file dialog (in this case, using wxPython):
>
> Traceback (most recent call last):
> File "boot_com_servers.py", line 21, in <module>
> File "C:\Python25\Lib\site-packages\pythoncom.py", line 3, in <module>
> pywintypes.__import_pywin32_system_module__("pythoncom", globals())
> File "C:\Python25\Lib\site-packages\win32\lib\pywintypes.py", line 98, in
> __import_pywin32_system_module__
> ('.dll', 'rb', imp.C_EXTENSION))
> ImportError: DLL load failed: The specified procedure could not be found.
>
>
> After reinstalling Win32Com on the computer, this is what I get:
>
> "Redirecting output to win32trace remote collector"
Believe it or not, it's actually pywin32 who's redirecting the stderr
and stdout.
My analysis so far has been, that when a file dialog is open,
pythoncom kicks in (in this case, triggered by TortoiseHg's overlay
icons extensions), forcing the redirection of std* to win32trace
collector. In the case of WingIDE, it has resulted in the hang-up (!)
of the whole application.
In the future release of TortoiseHg, we hope to replace the Explorer
shell extensions with a C++ version, which would hopefully get rid of
all the problems caused by the used of pythoncom in the current
implementation. The prototype for the C++ version is working.
> So I guess that proves that the installation of TortoiseHG does still break
> the pre-existing installation of win32com in Python25.
>
> I did not reboot the computer in the meantime.
>
> Also, the output that would normally be printed to stdout at this point, is
> now gone.
>
> I hope that this gives enough clues to determine what the problem is, and if
> there's a solution.
>
> Kind regards,
>
> --Tim
>
>
> On Thu, Aug 14, 2008 at 2:39 PM, Tim van der Leeuw <[EMAIL PROTECTED]>
> wrote:
>>
>> Hi,
>>
>> On Thu, Aug 14, 2008 at 2:16 PM, TK Soh <[EMAIL PROTECTED]> wrote:
>>>
>>> On Thu, Aug 14, 2008 at 12:10 PM, Tim van der Leeuw <[EMAIL PROTECTED]>
>>> wrote:
>>> > Hi,
>>> >
>>> > I've noticed that when I call an open-file dialog from a Python
>>> > program,
>>> > that TortoiseHG then swallows the stdout and stderr from that Python
>>> > program, and redirects it to where it puts it's own logging.
>>>
>>> What do mean by 'swallows'?
>>
>> Well, when I open a windows standard-file dialog, THG will display the
>> overlay-icons in that dialog too.
>> So when it starts, it tries to open and load some pywin32 pythoncom DLL,
>> which will redirect logging to a windows service (I believe).
>> Unfortunately it does that from the current Python process, uses the
>> current PythonPath to load the PyWin32 modules, and the output from the
>> current Python process will all be redirect to (I believe) the system event
>> logger.
>>
>> I'm sorry that I can't be more specific and can't paste the one last
>> message I do see in my stdout. The computer on which I am typing now cannot
>> install TortoiseHG, and the computer on which I do have these problems is
>> not currently on the net -- besides, I just installed a new THG version but
>> didn't yet reboot, so now all I get is a traceback with an importerror that
>> some Win32Com DLL cannot be loaded from
>> "C:\Python25\Lib\site-packages\pythoncom.py".
>> But I cann't copy-paste that traceback into the mail until tonight...
>>
>>
>> So I hope that I have now given enough information already to say
>> something about the problem, otherwise it will have to wait until later
>> today when my laptop can be hooked up to the internet again.
>>
>>
>>>
>>> > As a Python software developer, I quite dislike this behaviour.
>>> >
>>> > Is there any workaround available for this? Any way to turn off this
>>> > behaviour in THG? It is for me a strong reason to actually just not
>>> > install
>>> > THG, except there's no more separate all-in-one installer anymore.
>>>
>>> Take it easy. I am sure there are ways around the problem.
>>
>> I'm sorry. And even more sorry I am for not posting this problem some
>> months earlier, when I first discoverd it and realized what was happening.
>>
>>
>> BTW, I do have PythonWin / Win32com extensions installed. I discovered
>> earlier that after installing THG, I needed to reinstall them in order to be
>> able to use them. That at least appears to be fixed now... :-)
>
>
> See above - I now believe that it's not. Reinstalling win32com extensions
> fixed the tracktrace that appeared before reinstalling it. There is some
> interaction between my Python installation, and the Python program that's
> run for me from Windows Explorer.
>
>>
>> Regards,
>>
>> --Tim
>>
>
>
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Tortoisehg-discuss mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/tortoisehg-discuss
