On 21 May 2007, at 19:27, Gary Bernhardt wrote:
> On 5/21/07, Kevin Horton <[EMAIL PROTECTED]> wrote:
>> I'm working on a small application that will respond to user input
>> via the console. It is a very simple interface, with user input via
>> "raw_input()", and the application produces result
On 5/21/07, Kevin Horton <[EMAIL PROTECTED]> wrote:
> I'm working on a small application that will respond to user input
> via the console. It is a very simple interface, with user input via
> "raw_input()", and the application produces result via "print"
> statements. I'm using python 2.5.1 on O
I'm working on a small application that will respond to user input
via the console. It is a very simple interface, with user input via
"raw_input()", and the application produces result via "print"
statements. I'm using python 2.5.1 on OS X, installed via Fink, but
I'll also use the appli
Calder Coalson wrote:
>> That is exactly what modules and imports let you do.
> It really doesn't seem to be doing that, because I import a bunch of
> stuff and define it in my main file, then I import another file and it
> can't use the global variables and the modules imported in the main file.
Calder Coalson wrote:
> All I want to do is split up my file into multiple files,
Why not a simple execfile("otherprogram.py")?
All the code in otherprogram.py is executed as if it was typed into
the main program.
No namespace issues or import problems. (Not OOP either, in fact!)
Hope this he
