# HG changeset patch # User Arne Babenhauserheide # Date 1472166001 -7200 # Fri Aug 26 01:00:01 2016 +0200 # Node ID 9b571d9ee08e45b20590b1990e174cec30f70d8a # Parent 131a10dd0be3ff1304e3645c461e928cbad3be90 typo diff --git a/py2guile.org b/py2guile.org --- a/py2guile.org +++ b/py2guile.org @@ -657,7 +657,7 @@ print k #+END_SRC -/(These are synthetic code examples to show you all the interacting features as little space as possible. Make them three times as long and calling into external functions at every step, then you have something close to real code I read and wrote.)/ +/(These are synthetic code examples to show you all the interacting features in as little space as possible. Make them three times as long and calling into external functions at every step, then you have something close to real code I read and wrote.)/ Both of these expressions are valid Python, and they yield the same result, but in the tutorials I saw over the years, newcomers mostly learn the first style, not the second - and the first style is the original Python-syntax. When you see that second syntax in raw form, it looks really bolted-on and the parentheses only barely contain, how alien it is to the original Python: