Comments on: Python Gotchas http://blog.cons.org.nz/2006/09/04/python-gotchas/ (cons web log) Tue, 08 Nov 2011 00:39:45 +0000 hourly 1 http://wordpress.org/?v=3.0.5 By: anon http://blog.cons.org.nz/2006/09/04/python-gotchas/#comment-18892 anon Mon, 11 Aug 2008 11:05:49 +0000 http://blog.cons.org.nz/?p=22#comment-18892 1/ "print" is not an expression in python, but an instruction (you can write "print 42" (or even "print >> sys.stderr, 42"), whom syntax clearly shows it's not an expression), so can't be included where an expression is expected => not a gotcha (in python 3000, "print" becomes a function (thus an expression too), and the "print 42" syntax is not valid then) 2/ python, like scheme or many well-designed languages, has lexical scoping, so "base" leaks in "inc" for reading, but python doesn't like mixing scopes for a same name ; you read the more external scope OR you write it in local scope, and then it refers only to local scope => semi-gotcha 1/ “print” is not an expression in python, but an instruction (you can write “print 42″ (or even “print >> sys.stderr, 42″), whom syntax clearly shows it’s not an expression), so can’t be included where an expression is expected => not a gotcha (in python 3000, “print” becomes a function (thus an expression too), and the “print 42″ syntax is not valid then)
2/ python, like scheme or many well-designed languages, has lexical scoping, so “base” leaks in “inc” for reading, but python doesn’t like mixing scopes for a same name ; you read the more external scope OR you write it in local scope, and then it refers only to local scope => semi-gotcha

]]> By: lorne http://blog.cons.org.nz/2006/09/04/python-gotchas/#comment-4232 lorne Mon, 04 Sep 2006 09:23:44 +0000 http://blog.cons.org.nz/?p=22#comment-4232 Fixed, thank you. Fixed, thank you.

]]> By: qwandor http://blog.cons.org.nz/2006/09/04/python-gotchas/#comment-4231 qwandor Mon, 04 Sep 2006 09:20:13 +0000 http://blog.cons.org.nz/?p=22#comment-4231 There is a typo in your links to the COMP312 and COMP304 pages. There is a typo in your links to the COMP312 and COMP304 pages.

]]>