mathdatech/python_reference
1
0
Fork 0
mirror of https://github.com/rasbt/python_reference.git synced 2025-03-20 20:49:53 +00:00
Code Issues Packages Projects Releases Wiki Activity

fixed for-loop example

Browse Source
This commit is contained in:
Sebastian Raschka 2014-04-29 21:38:56 -04:00
parent c3fc8395e2
commit 3e6588120f
1 changed files with 8 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
tutorials/scope_resolution_legb_rule.ipynb
View File

@ -593,7 +593,8 @@
"cell_type": "markdown",
"metadata": {},
"source": [
"Similar to the concept of the `global` keyword, which we have seen in the section above, we can use the keyword `nonlocal` inside the inner function to explicitely access a variable from the outer (enclosed) scope in order to modify its value:"
"Similar to the concept of the `global` keyword, which we have seen in the section above, we can use the keyword `nonlocal` inside the inner function to explicitely access a variable from the outer (enclosed) scope in order to modify its value. \n",
"Note that the `nonlocal` keyword was added in Python 3.x and is not implemented in Python 2.x (yet)."
]
},
{
@ -1045,12 +1046,13 @@
]
},
{
"cell_type": "code",
"collapsed": false,
"input": [],
"language": "python",
"cell_type": "markdown",
"metadata": {},
"outputs": []
"source": [
"This goes back to a change that was made in Python 3.x and is described in [What\u2019s New In Python 3.0](https://docs.python.org/3/whatsnew/3.0.html) as follows:\n",
"\n",
"\"List comprehensions no longer support the syntactic form `[... for var in item1, item2, ...]`. Use `[... for var in (item1, item2, ...)]` instead. Also note that list comprehensions have different semantics: they are closer to syntactic sugar for a generator expression inside a `list()` constructor, and in particular the loop control variables are no longer leaked into the surrounding scope.\""
]
}
],
"metadata": {}