On 11/14/2011 10:00 AM, John Gordon wrote:
In "W. eWatson" writes:
I would think the install would make the association of py to Python,
either IDLE or the interpreter.
I would hope so too, however you did mention that you moved the python
executable to a different directory and installed a
In "W. eWatson" writes:
> I would think the install would make the association of py to Python,
> either IDLE or the interpreter.
I would hope so too, however you did mention that you moved the python
executable to a different directory and installed a newer version, so
verifying that the .py
On 11/14/2011 8:15 AM, John Gordon wrote:
In "W. eWatson" writes:
What application is associated with .py files?
Application? Simple ones, including the one i put here that you
removed to answer my question.
Eh? I can't see anywhere that you mentioned your Windows settings as
to what ap
In "W. eWatson" writes:
> > What application is associated with .py files?
> Application? Simple ones, including the one i put here that you
> removed to answer my question.
Eh? I can't see anywhere that you mentioned your Windows settings as
to what application is associated with .py files.
On 11/14/2011 7:24 AM, John Gordon wrote:
In "W. eWatson" writes:
I just pushed aside the python25 folder by renaming it, and installed py
2.5.2. However, when I try to open the simplest of py programs with
IDLE, I get an error from Win7.
c:\Users\blah\...\junk.py is not a valid Win 32 app
In "W. eWatson" writes:
> I just pushed aside the python25 folder by renaming it, and installed py
> 2.5.2. However, when I try to open the simplest of py programs with
> IDLE, I get an error from Win7.
> c:\Users\blah\...\junk.py is not a valid Win 32 app.
Are you double-clicking on the .py
I just pushed aside the python25 folder by renaming it, and installed py
2.5.2. However, when I try to open the simplest of py programs with
IDLE, I get an error from Win7.
c:\Users\blah\...\junk.py is not a valid Win 32 app.
Here's one:
def abc(one):
print "abc: ", one, " is one"
def duh
