Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
Message from discussion Checking for dlls in ctypes
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Wanderer  
View profile  
 More options Oct 12 2012, 1:57 pm
Newsgroups: comp.lang.python
From: Wanderer <wande...@dialup4less.com>
Date: Fri, 12 Oct 2012 10:57:09 -0700 (PDT)
Local: Fri, Oct 12 2012 1:57 pm
Subject: Re: Checking for dlls in ctypes

On Friday, October 12, 2012 12:29:02 PM UTC-4, Dave Angel wrote:
> On 10/12/2012 11:36 AM, Wanderer wrote:

> > I'm trying to write some code that will load one of three dll depending on the one available. I've tried the code below, but it doesn't work. The try except doesn't catch the exception. Is there a way to do this?

> >         try:

> >             self.dll = windll.pvcam64

> >         except:

> >             print "No pvcam64"

> >             try:

> >                 self.dll = windll.pvcam32

> >             except:

> >                 print "No pvcam32"

> >                 try:

> >                     self.dll = windll.pvcam

> >                 except:

> >                     print "No pvcam"

> >                     return

> >                 else:

> >                     print "installed pvcam"

> >             else:

> >                 print "installed pvcam32"

> >         else:

> >             print "installed pvcam64"

> I can't help you find the dll's, because I don't run Windows.  But I

> could help you write a clearer question:

> "doesn't work" is thoroughly useless for describing errors.  If you're

> getting an exception, show us the full traceback.  That will show which

> statement got the exception that wasn't caught.  Next question is which

> of the dlls is missing.  Are you getting an exception because it's

> missing or because of something more fundamental, like nesting exception

> handlers?

> Using bare excepts is almost never a good idea.  If it "works" you get

> no clues what went wrong.  For example, a typo in source code can

> trigger a bare exception, as can a user typing Ctrl-C.   So when you're

> using bare excepts, you have robbed the user of any way to terminate the

> program.

> If I were you, I'd be writing a loop so there's only one try block.  Too

> much duplicated code in the way you're doing it.

> --

> DaveA

Sorry. It was a WindowsError, but the code I posted now works for me and I can't reproduce the problem. I'll be more diligent in the future.

 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.