[python-win32] calling a dll after python 2.3 pywin32-208

Mark Hammond mhammond at skippinet.com.au
Mon May 14 14:50:40 CEST 2012


[re-adding python-win32 - please keep replies on list]

On 14/05/2012 10:39 PM, EdShallow wrote:
> Hi Mark,
>
>       Python 2.3 with pywin32-208 works. The error I receive reads
> "Object through and exception at line 3".

How do you get that error?  You say "my dll throws an exception 
immediately upon entry" - I can't reconcile that "with the error I 
receive".  What does Python do when calling your failing DLL?  (ie, do 
you get a traceback?  If so, please include it completely.  If not, what 
result does Python get?  I'm still very unclear on the context of your 
problem.

>       Un-registering and re-registering the dll does not help.

But that's just unregistering and re-registering your DLL right?

>       The test was conducted on the same machine after uninstalling
> Python and re-installing numerous combinations of Python 2.4, 2.5, 2.6,
> 2.7 with associated pywin32-208 thry pywin32-214.
>
>      If I uninstall the newer Python and re-install Python 2.3 and
> pywin32-208 all is OK again. It is definitely environmental as opposed
> to the code.

Well - it's *someone's* code :)  To be clear, 2.3 + pywin32 209 fails?

Mark
>
> Thanks,
> Ed
>
> On Sun, May 13, 2012 at 9:07 PM, Mark Hammond <skippy.hammond at gmail.com
> <mailto:skippy.hammond at gmail.com>> wrote:
>
>     You haven't given us enough information to help.  What error do you
>     see?  What is the most recent combination of Python and pywin32 that
>     works?
>
>     Mark
>
>
>     On 12/05/2012 10:31 PM, EdShallow wrote:
>
>         Hi Folks,
>
>               I have an ActiveX COM dll generated by VisualBasic 6 in
>         WinXP. I
>         can call it and use it successfully with Python 2.3 and pywin32-208
>         without problems.
>
>               As soon as I upgrade either pywin32- or Python to anything
>         itself
>         to anything newer, my dll throws an exception immediately upon
>         entry.
>
>               Can anyone point me in a general direction with respect to
>         addressing this incompatibility?
>
>         Thanks,
>         Ed
>
>         --
>         Ed's Contact Information:
>         Mobile Phone: 613-852-6410 <tel:613-852-6410>
>         Gmail: ed.shallow at gmail.com <mailto:ed.shallow at gmail.com>
>         <mailto:ed.shallow at gmail.com <mailto:ed.shallow at gmail.com>>
>         VOIP Address: 107529 at sip.ca1.voip.ms
>         <mailto:107529 at sip.ca1.voip.ms> <mailto:107529 at sip.ca1.voip.ms
>         <mailto:107529 at sip.ca1.voip.ms>__>
>
>         VOIP DID#: 613-458-5004 <tel:613-458-5004>
>         Skype ID: edward.shallow
>         Home Phone: 613-482-2090 <tel:613-482-2090>
>
>
>
>         _________________________________________________
>         python-win32 mailing list
>         python-win32 at python.org <mailto:python-win32 at python.org>
>         http://mail.python.org/__mailman/listinfo/python-win32
>         <http://mail.python.org/mailman/listinfo/python-win32>
>
>
>
>
>
>
> --
> Ed's Contact Information:
> Mobile Phone: 613-852-6410
> Gmail: ed.shallow at gmail.com <mailto:ed.shallow at gmail.com>
> VOIP Address: 107529 at sip.ca1.voip.ms <mailto:107529 at sip.ca1.voip.ms>
> VOIP DID#: 613-458-5004
> Skype ID: edward.shallow
> Home Phone: 613-482-2090
>




More information about the python-win32 mailing list