ee1e8abd87
* feat(tools): add seed/solution restore script * chore(curriculum): remove empty sections' markers * chore(curriculum): add seed + solution to Chinese * chore: remove old formatter * fix: update getChallenges parse translated challenges separately, without reference to the source * chore(curriculum): add dashedName to English * chore(curriculum): add dashedName to Chinese * refactor: remove unused challenge property 'name' * fix: relax dashedName requirement * fix: stray tag Remove stray `pre` tag from challenge file. Signed-off-by: nhcarrigan <nhcarrigan@gmail.com> Co-authored-by: nhcarrigan <nhcarrigan@gmail.com>
44 lines
932 B
Markdown
44 lines
932 B
Markdown
---
|
|
id: 5e9a093a74c4063ca6f7c165
|
|
title: Python Introduction
|
|
challengeType: 11
|
|
videoId: PrQV9JkLhb4
|
|
dashedName: python-introduction
|
|
---
|
|
|
|
# --description--
|
|
|
|
*Instead of using notebooks.ai like it shows in the video, you can use Google Colab instead.*
|
|
|
|
More resources:
|
|
|
|
- [Notebooks on GitHub](https://github.com/ine-rmotr-curriculum/ds-content-python-under-10-minutes)
|
|
- [How to open Notebooks from GitHub using Google Colab.](https://colab.research.google.com/github/googlecolab/colabtools/blob/master/notebooks/colab-github-demo.ipynb)
|
|
|
|
# --question--
|
|
|
|
## --text--
|
|
|
|
How do we define blocks of code in the body of functions in Python?
|
|
|
|
## --answers--
|
|
|
|
We use a set of curly braces, one on either side of each new block of our code.
|
|
|
|
---
|
|
|
|
We use indentation, usually right-aligned 4 spaces.
|
|
|
|
---
|
|
|
|
We do not denote blocks of code.
|
|
|
|
---
|
|
|
|
We could use curly braces or indentation to denote blocks of code.
|
|
|
|
## --video-solution--
|
|
|
|
2
|
|
|