[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Discuss-gnuradio] Booting a new USRP
From: |
Matt Ettus |
Subject: |
Re: [Discuss-gnuradio] Booting a new USRP |
Date: |
Sat, 19 Feb 2005 08:59:57 -0800 |
User-agent: |
Internet Messaging Program (IMP) 4.0-cvs |
Quoting John Gilmore <address@hidden>:
> In general I wonder -- is it the practice in Python to have "includes"
> run off and do things that could cause errors? I'm used to more static
> languages where if you import a library, it just lays there until you call
> it. :-) That way, you can parse your arguments and produce your error
> messages, and maybe never even call that included package, depending on
> the options you were passed.
You can put the import statements in a try block so that you can gracefully
handle exceptions. For some reason, nobody ever seems to do this, but I did it
in some of the early SDR-1000 code I checked in.
Matt
- Re: [Discuss-gnuradio] Bug in usrper.cc, (continued)
- Re: [Discuss-gnuradio] Bug in usrper.cc, Eric Blossom, 2005/02/08
- Re: [Discuss-gnuradio] Booting a new USRP, Rahul Dhar, 2005/02/11
- Re: [Discuss-gnuradio] Booting a new USRP, cfk, 2005/02/11
- Re: [Discuss-gnuradio] Booting a new USRP, Rahul Dhar, 2005/02/11
- [Discuss-gnuradio] usrp_oscope.py, cfk, 2005/02/11
- Re: [Discuss-gnuradio] usrp_oscope.py, Eric Blossom, 2005/02/11
- Re: [Discuss-gnuradio] Booting a new USRP, Eric Blossom, 2005/02/11
- Re: [Discuss-gnuradio] Booting a new USRP, John Gilmore, 2005/02/18
- Re: [Discuss-gnuradio] Booting a new USRP, Eric Blossom, 2005/02/18
- Re: [Discuss-gnuradio] Booting a new USRP, John Gilmore, 2005/02/19
- Re: [Discuss-gnuradio] Booting a new USRP,
Matt Ettus <=
- Re: [Discuss-gnuradio] Booting a new USRP, Eric Blossom, 2005/02/19
- Re: [Discuss-gnuradio] Booting a new USRP, Eric Blossom, 2005/02/11
Re: [Discuss-gnuradio] FC3 build problems, Chris, 2005/02/04