On Friday, February 20, 2009 9:41:42 AM UTC-6, David Smith wrote:
What I meant was open open the command prompt, type cd, space, DO NOT
hit enter yet. Drag the folder with your script into the command prompt
window. Then go to the command prompt window and hit enter. This
should compose a
On Mon, Jul 16, 2012 at 1:35 AM, rantingrickjohn...@gmail.com wrote:
Besides, you can skip most of those steps by Shift+RightClicking the file
icon and choosing Open Command Window Here.
That's not standard. Me, I can invoke git bash anywhere I want it, but
that doesn't mean I'd recommend
On Sunday, July 15, 2012 10:57:00 AM UTC-5, Chris Angelico wrote:
On Mon, Jul 16, 2012 at 1:35 AM, rantingrickjohn...@gmail.com wrote:
Besides, you can skip most of those steps by Shift+RightClicking
the file icon and choosing Open Command Window Here.
That's not standard. Me, I can invoke
On Mon, Jul 16, 2012 at 2:19 AM, Rick Johnson
rantingrickjohn...@gmail.com wrote:
On Sunday, July 15, 2012 10:57:00 AM UTC-5, Chris Angelico wrote:
On Mon, Jul 16, 2012 at 1:35 AM, rantingrickjohn...@gmail.com wrote:
Besides, you can skip most of those steps by Shift+RightClicking
the file
On Thursday, February 19, 2009 10:06:42 PM UTC-6, W. eWatson wrote:
I'm using IDLE for editing, but execute programs directly. If there are
execution or compile errors, the console closes before I can see what it
contains. How do I prevent that?
Q: If you are in fact using IDLE to edit your
On Friday, February 20, 2009 4:06:42 AM UTC, W. eWatson wrote:
I#39;m using IDLE for editing, but execute programs directly. If there are
execution or quot;compilequot; errors, the console closes before I can see
what it
contains. How do I prevent that?
--
I think you can use pythonw.exe which will read stdin and for any
input before closing.
(I read this a while back, ma guy here.)
Sent from my iPhone
On Jul 13, 2012, at 7:27 AM, summerholidaylearn...@gmail.com
summerholidaylearn...@gmail.com wrote:
On Friday, February 20, 2009 4:06:42 AM UTC,
Matimus wrote:
On Feb 19, 8:06 pm, W. eWatson notval...@sbcglobal.net wrote:
I'm using IDLE for editing, but execute programs directly. If there are
execution or compile errors, the console closes before I can see what it
contains. How do I prevent that?
--
W.
W. eWatson wrote:
Matimus wrote:
On Feb 19, 8:06 pm, W. eWatson notval...@sbcglobal.net wrote:
I'm using IDLE for editing, but execute programs directly. If there are
execution or compile errors, the console closes before I can see
what it
contains. How do I prevent that?
--
On Feb 19, 2009, at 23:06 , W. eWatson wrote:
I'm using IDLE for editing, but execute programs directly.
Is there a reason you are executing them directly? Why not just run
the script from IDLE with Run/Run Module (F5) until you are sure
there are no errors? You can follow the advice
I'm not sure whether I should feel old or write a smart alec comment --
I suppose there are people in the world who don't know what to do with a
command prompt
Assuming a Windows system:
2. Type 'cd ' (as in Change Directory) in the command prompt window (w/o
the single quote characters)
W. eWatson wrote:
I'm not sure whether I should feel old or write a smart alec comment --
I suppose there are people in the world who don't know what to do with a
command prompt
Assuming a Windows system:
2. Type 'cd ' (as in Change Directory) in the command prompt window (w/o
the
W. eWatson wrote:
I'm not sure whether I should feel old or write a smart alec comment --
I suppose there are people in the world who don't know what to do with a
command prompt
Assuming a Windows system:
2. Type 'cd ' (as in Change Directory) in the command prompt window (w/o
the
En Fri, 20 Feb 2009 12:05:08 -0200, W. eWatson notval...@sbcglobal.net
escribió:
Whoa! What's going on here? I just looked at About IDLE, and it shows
1.2.2, but yet the second edition of Learning Python talks about going
to 2.3 as the book is about to go to press, 2004. I thought IDLE
Gabriel Genellina wrote:
En Fri, 20 Feb 2009 12:05:08 -0200, W. eWatson notval...@sbcglobal.net
escribió:
Whoa! What's going on here? I just looked at About IDLE, and it shows
1.2.2, but yet the second edition of Learning Python talks about going
to 2.3 as the book is about to go to press,
Catherine Heathcote wrote:
W. eWatson wrote:
I'm not sure whether I should feel old or write a smart alec comment --
I suppose there are people in the world who don't know what to do with a
command prompt
Assuming a Windows system:
2. Type 'cd ' (as in Change Directory) in the command
W. eWatson wrote:
Catherine Heathcote wrote:
W. eWatson wrote:
I'm not sure whether I should feel old or write a smart alec comment --
I suppose there are people in the world who don't know what to do
with a
command prompt
Assuming a Windows system:
2. Type 'cd ' (as in Change
En Fri, 20 Feb 2009 12:29:35 -0200, W. eWatson notval...@sbcglobal.net
escribió:
Gabriel Genellina wrote:
En Fri, 20 Feb 2009 12:05:08 -0200, W. eWatson
notval...@sbcglobal.net escribió:
Whoa! What's going on here? I just looked at About IDLE, and it shows
1.2.2, but yet the second
En Fri, 20 Feb 2009 12:39:14 -0200, W. eWatson notval...@sbcglobal.net
escribió:
Catherine Heathcote wrote:
you need to open a dos prompt before doing the steps above. Go to
start-run and hit cmd enter without the quotes.
Something is amiss here. There's the MS Command Prompt, which I'm
Catherine Heathcote wrote:
W. eWatson wrote:
Catherine Heathcote wrote:
W. eWatson wrote:
I'm not sure whether I should feel old or write a smart alec
comment --
I suppose there are people in the world who don't know what to do
with a
command prompt
Assuming a Windows system:
2.
Gabriel Genellina wrote:
En Fri, 20 Feb 2009 12:29:35 -0200, W. eWatson notval...@sbcglobal.net
escribió:
Gabriel Genellina wrote:
En Fri, 20 Feb 2009 12:05:08 -0200, W. eWatson
notval...@sbcglobal.net escribió:
Whoa! What's going on here? I just looked at About IDLE, and it
shows 1.2.2,
W. eWatson wrote:
I'm not sure whether I should feel old or write a smart alec comment --
I suppose there are people in the world who don't know what to do with a
command prompt
Assuming a Windows system:
2. Type 'cd ' (as in Change Directory) in the command prompt window (w/o
the
W. eWatson wrote:
Catherine Heathcote wrote:
W. eWatson wrote:
Catherine Heathcote wrote:
W. eWatson wrote:
I'm not sure whether I should feel old or write a smart alec
comment --
I suppose there are people in the world who don't know what to do
with a
command prompt
Assuming a
David Smith wrote:
W. eWatson wrote:
I'm not sure whether I should feel old or write a smart alec comment --
I suppose there are people in the world who don't know what to do with a
command prompt
Assuming a Windows system:
2. Type 'cd ' (as in Change Directory) in the command prompt
En Fri, 20 Feb 2009 13:37:06 -0200, W. eWatson notval...@sbcglobal.net
escribió:
Catherine Heathcote wrote:
W. eWatson wrote:
Run the program from within the MS command line, not by double
clicking it.
Shirley, you jest? DOS? To do this? How ugly. I barely recall the DOS
commands. I get
Catherine Heathcote wrote:
W. eWatson wrote:
Catherine Heathcote wrote:
W. eWatson wrote:
I'm not sure whether I should feel old or write a smart alec
comment --
I suppose there are people in the world who don't know what to do
with a
command prompt
Assuming a Windows system:
2.
W. eWatson wrote:
David Smith wrote:
W. eWatson wrote:
I'm not sure whether I should feel old or write a smart alec comment --
I suppose there are people in the world who don't know what to do
with a
command prompt
Assuming a Windows system:
2. Type 'cd ' (as in Change Directory) in
On Feb 19, 8:06 pm, W. eWatson notval...@sbcglobal.net wrote:
I'm using IDLE for editing, but execute programs directly. If there are
execution or compile errors, the console closes before I can see what it
contains. How do I prevent that?
--
W. eWatson
28 matches
Mail list logo
