[Tutor] Python Idle Crashing

Prasad, Ramit ramit.prasad at jpmorgan.com
Fri May 17 21:35:39 CEST 2013


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 <ramit.prasad at jpmorgan.com> 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 developing
> > > programs not running them.
> >
> > That is really scary. Why do you say that? The IDLE documentation does
> > NOT say that!
> 
> Python is a GREAT learning language, but it's also a tool for Getting Stuff Done in the Real World.
> When you send your programs out into the wide world, it makes a really poor impression if you have to
> instruct your users to open an IDE first, load your script, and then press F5.  So at the very least,
> you should get into the habit of making your scripts work outside of IDLE, or whatever IDE you
> prefer.  (If nobody but you will ever run your stuff, I suppose this doesn't matter so much - but in
> that case, what Alan said about 'real data' doesn't apply either.)
> In addition, I find that the Tk-ness of IDLE interferes with any other GUI library you might prefer -
> I use wxPython, and while IDLE is great for quickly diagnosing the sorts of errors that prevent my
> programs from putting anything on the screen to begin with, it gets very crashy once wx gets
> initialized.  IDLE is a bit like the prize in CrackerJack - it's a nice extra, but it certainly
> shouldn't be the reason you bought the box!



This email is confidential and subject to important disclaimers and
conditions including on offers for the purchase or sale of
securities, accuracy and completeness of information, viruses,
confidentiality, legal privilege, and legal entity disclaimers,
available at http://www.jpmorgan.com/pages/disclosures/email.  


More information about the Tutor mailing list