Python is going to be hard

Rustom Mody rustompmody at gmail.com
Thu Sep 4 15:08:27 CEST 2014


On Thursday, September 4, 2014 3:59:57 PM UTC+5:30, alister wrote:
> On Wed, 03 Sep 2014 19:33:41 -0700, Rustom Mody wrote:

> > On Thursday, September 4, 2014 7:56:31 AM UTC+5:30, Chris Angelico
> > wrote:
> >> When you start a script, you have a consistent environment - an empty
> >> one. When you write a series of commands in the interactive
> >> interpreter, the environment for each one depends on all the preceding
> >> commands. So when you have a problem, you might have to copy and paste
> >> the entire interpreter session, rather than just the one command.
> > Agreed. Thats a downside.
> > Very minor compared to the mess induced by unstructured print-filled
> > noob code.

> until the New programmer (I hate the word noob, it looks too derogatory 
> even when that is not the intention) has learnt enough to be using a 
> logging module i can see no alternative to using print for debugging 
> purposes.

Fully agree. If the one giving the instruction makes it clear that
this thing called a print statement (expression) is something -- a
probe -- you stick into the program to figure out whats happening,
thats fine.  If its presented as something that a program can have any
amount of then its not.





More information about the Python-list mailing list