On 05/17/2013 02:19 PM, Alan Gauld wrote:
On 17/05/13 18:16, bob gailer wrote:
On 5/16/2013 8:49 PM, Alan Gauld wrote:
don't run programs on real data using IDLE. IDLE is for developing
programs not running them.
That is really scary. Why do you say that? The IDLE documentation does
NOT say
On Fri, May 17, 2013 at 12:35 PM, Prasad, Ramit
wrote:
> Forwarding to the list as I believe the reply was mistakenly sent only to
> me.
>
Grr. Sorry about that!
___
Tutor maillist - Tutor@python.org
To unsubscribe or change subscription options:
http
Forwarding to the list as I believe the reply was mistakenly sent only to me.
Marc Tompkins wrote:
> On Fri, May 17, 2013 at 11:08 AM, Prasad, Ramit
> wrote:
> bob gailer wrote:
> >
> > On 5/16/2013 8:49 PM, Alan Gauld wrote:
> > > don't run programs on real data using IDLE. IDLE is for developi
bob gailer wrote:
>
> On 5/16/2013 8:49 PM, Alan Gauld wrote:
> > don't run programs on real data using IDLE. IDLE is for developing
> > programs not running them.
>
> That is really scary. Why do you say that? The IDLE documentation does
> NOT say that!
Relates to IDEs and not IDLE in specific.
On 17/05/13 18:16, bob gailer wrote:
On 5/16/2013 8:49 PM, Alan Gauld wrote:
don't run programs on real data using IDLE. IDLE is for developing
programs not running them.
That is really scary. Why do you say that? The IDLE documentation does
NOT say that!
No, but IDLE is *intended* for devel
On 18/05/13 03:16, bob gailer wrote:
On 5/16/2013 8:49 PM, Alan Gauld wrote:
don't run programs on real data using IDLE. IDLE is for developing programs not
running them.
That is really scary. Why do you say that? The IDLE documentation does NOT say
that!
IDLE is an IDE, that is, Integrate
On 5/16/2013 8:49 PM, Alan Gauld wrote:
don't run programs on real data using IDLE. IDLE is for developing
programs not running them.
That is really scary. Why do you say that? The IDLE documentation does
NOT say that!
--
Bob Gailer
919-636-4239
Chapel Hill NC
__
kyle seebohm wrote:
> I recently created a program that searches through a computer's drive to
> make a list of all the files in that drive. However, the drive I am
> attempting to parse through is extremely large and when I run my program,
> it runs for about 5 or 10 minutes then proceeds to not
On 16/05/13 19:17, kyle seebohm wrote:
I recently created a program that searches through a computer's drive to
make a list of all the files in that drive. However, the drive I am
attempting to parse through is extremely large and when I run my
program, it runs for about 5 or 10 minutes then proc
Dave Angel wrote:
> On 05/16/2013 02:17 PM, kyle seebohm wrote:
> > I recently created a program that searches through a computer's drive to
> > make a list of all the
> files in that drive. However, the drive I am attempting to parse through is
> extremely large and when I
> run my program, it r
On 05/16/2013 02:17 PM, kyle seebohm wrote:
I recently created a program that searches through a computer's drive to make a
list of all the files in that drive. However, the drive I am attempting to
parse through is extremely large and when I run my program, it runs for about 5
or 10 minutes t
I don't think running this on Idle is the best.
Did you try to run your program in the command line?
___
Tutor maillist - Tutor@python.org
To unsubscribe or change subscription options:
http://mail.python.org/mailman/listinfo/tutor
I recently created a program that searches through a computer's drive to make a
list of all the files in that drive. However, the drive I am attempting to
parse through is extremely large and when I run my program, it runs for about 5
or 10 minutes then proceeds to not respond and not finish par
13 matches
Mail list logo
