<br><br><div><span class="gmail_quote">On 8/3/07, <b class="gmail_sendername">kirby urner</b> <<a href="mailto:kirby.urner@gmail.com">kirby.urner@gmail.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On 8/3/07, Andre Roberge <<a href="mailto:andre.roberge@gmail.com">andre.roberge@gmail.com</a>> wrote:<br><br>> Kirby got a good point - however, I think that you'd still get the "hook"<br>> with newbies without the automatic echoing that Michael describes.
<br>><br><br>Not sure we should call this "echoing" as what's happening<br>is an expression is being evaluated.<br><br>It just so happens that the eval of a quoted string returns<br>itself whereas "some expression with %s" % "substitution"
<br>would actually evaluate to non-echo.<br><br>kirby@dell:~$ python ./repl.py<br>>>> 'THIS IS A STRING'<br>THIS IS A STRING<br>>>> [x*x for x in range(10)]<br>[0, 1, 4, 9, 16, 25, 36, 49, 64, 81]
<br>>>> "1-2-3 %s" % "testing"<br>1-2-3 testing<br><br>Would one turn off all of the above, or just the first eval-print?<br><br>What would be the point of a broken shell, vs explaining that<br>
Python, like many languages, features a REPL (read-eval-print loop)?<br><br>Kirby<br></blockquote></div>I don't see it as "either or", but as "why not allow both?". I agree entirely with the strength of the REPL. However, when going from that to having code saved in a file and executed, a huge step occurs (which is what Michael was referring to I believe) in that to see something output, the user *must* put in an explicit print statement.
<br><br>What I envisage right now is to continue to have the default shell using in Crunchy (prompt = ">>>") and give the possibility to have a "parrot" shell (obligatory Monty Python reference; he's not dead. He may not be replying ... but he's just sleeping). Perhaps the prompt could be
<br><br>u_) (parrot lying on its side, two feet up, beak pointing up; sorry Kirby, the parrot's ribs are too small to see).<br><br>I could see a teacher giving a few interactive examples with this shell, have the students play with it for a short while, and then move on to saving files and running them. ... Just something to ease the transition from the friendly REPL to writing standalone scripts.
<br><br>@Michael: is this what you had in mind?<br><br>André<br>