#
# Header 1 |
# Header 2 |
#
#
# row 1, cell 1 |
# row 1, cell 2 |
#
#
# row 2, cell 1 |
# row 2, cell 2 |
#
#
# ## Github Flavored Markdown
# The Notebook webapp support Github flavored markdown meaning that you can use triple backticks for code blocks
#
# ```python
# print("Hello World")
# ```
#
# ```javascript
# console.log("Hello World")
# ```
#
#
# Gives
# ```python
# print("Hello World")
# ```
#
# ```javascript
# console.log("Hello World")
# ```
#
# And a table like this :
#
#
# | This | is |
# |------|------|
# | a | table|
#
#
# A nice Html Table
#
# | This | is |
# |------|------|
# | a | table|
# ## Local files
# In[2]:
get_ipython().system('ls *svg *m4v')
# If you have local files in your Notebook directory, you can refer to these files in Markdown cells via relative URLs that are prefixed with `files/`:
#
# files/[subdirectory/]
#
# Note that it is **not** `/files`.
#
# For example, in the `figs` subdirectory, we have the Python logo:
#
# ![img](files/python-logo.svg)
#
# and a video with the HTML5 video tag:
#
#
#
# These do not embed the data into the notebook file, and require that the files exist when you are viewing the notebook.
# ### Exercise
# Download a photo from the web into the local directory, and display it in the notebook by using the files URL pattern explained above
# ### Security of local files
# Note that this means that the Jupyter notebook server also acts as a generic file server
# for files inside the same tree as your notebooks. Access is not granted outside the
# notebook folder so you have strict control over what files are visible, but for this
# reason it is highly recommended that you do not run the notebook server with a notebook
# directory at a high level in your filesystem (e.g. your home directory).
#
# When you run the notebook in a password-protected manner, local file access is restricted
# to authenticated users unless read-only views are active.