Thanks, Alan. Some of what I've derived elsewhere almost sounds like
hearsay or is anecdotal. I'm thinking here about forums and the like.
However, I just grabbed my Core Python book, and noted than Chun
mentions a preferred sequence.
Std Lib, Third Party, App specific modules. He cites scoping rules.
Another question on similar matters. If I write a program and "compile"
it for distribution, and a user has 2.6 going to be able to execute it.
I would like to the the compiled program is free of such restrictions.
That is, it's an independent program. I would like to think that if I've
been testing it successfully in IDLE, that the compiled version will
produce everything I see in IDLE. For example, when I run it in IDLE,
and make a connection to the (camera) h/w, a dos-like window appears
that I otherwise never see. The program purposefully either sends
warning and error messages there through some built-in facility or
creates that window somehow. I'm dealing with tkinter in the app code. I
didn't write the (1600 line) program, but certainly am modifying it.
On 2/13/2010 1:33 AM, Alan Gauld wrote:
"Wayne Watson" <sierra_mtnv...@sbcglobal.net> wrote
There seems to be something of a general consensus in ordering import
statements. Something like standard library imports first.
I've never seen anything written down but its true I tend to do that.
But its not been a conscious thing...
...
--
"Crime is way down. War is declining. And that's far from the good
news." -- Steven Pinker (and other sources) Why is this true, but yet
the media says otherwise? The media knows very well how to manipulate us
(see limbic, emotion, $$). -- WTW
_______________________________________________
Tutor maillist - Tutor@python.org
To unsubscribe or change subscription options:
http://mail.python.org/mailman/listinfo/tutor
