5Standalone Script

Using Atom's Hydorgen package, you can execute any Python script codes within a fenced code block in a Markdown source. So you can edit your code verifying its execution results. But unfortunately (as long as I know), the entire Markdown source cannot be executed all at once as a standalone script and cannot be ran by Python interpreter. Pheasant connects between a pure Python script and a Markdown source. Actually, this page is written by a pure Python code.

5.1How to

A basic idea is that Markdown cells and Python code cells generally appear alternately. We can write a Markdown cell with a successive comment lines. In order to be recognized as a Markdown cell, # must be at the begining of lines. But we can insert a blank line to make a paragraph.

Normal Python code is treated as a code cell as you expect. A code cell can contain any comments as long as the comments don't start at the begining of line.

When a comment starts at the begining of line after a code block, it divides the source into a code cell and a Markdown cell. This new Markdown cell will continue until next Python code appears.

If you want to include a comment at the begining of line, you can write like this:

# !First comment in a code cell.
a = 1

becomes

# First comment in a code cell.
a = 1

[2]2019-05-12 09:32:45 (9.02ms)
python3 (2.26s)

Despite of a Markdown cell, you may want to devide successive codes into separate cells. This can be done by putting a special inline comment to define a cell. The comment pattern is # - or # %%. For example,

# * a markdown cell
a, b, c = 1, 2, 3
a
# -
b
# %%
c

becomes

a markdown cell

a, b, c = 1, 2, 3
a

[3]2019-05-12 09:32:45 (8.00ms)
python3 (2.27s)

1

b

[4]2019-05-12 09:32:46 (13.0ms)
python3 (2.28s)

2

c

[5]2019-05-12 09:32:46 (7.00ms)
python3 (2.29s)

3

You can add options to a code block by adding them after a cell devider.

# %% hide
d = 4
# * Output: `d` is equal to {{d}}.

Above python code is equivalent to the next Markdown source.

```python hide
d = 4
```
* Output: `d` is equal to {{d}}.

Then you can hide the python code cell.

Output: d is equal to 4.

5.2Fenced code block in Python source

You can write a fenced code block in a Python source as comment.

# ```python
# print(1)
# ```

becomes:

print(1)

[8]2019-05-12 09:32:46 (7.01ms)
python3 (2.31s)

1

And,

# ~~~
# ```python
# print(1)
# ```
# ~~~

becomes:

```python
print(1)
```

5.3A package for comment formatting

In this scheme, we have to write many comments for Markdown cells. But a linter such as pycodestyle doesn't allow us to write a very long comment in one line longer than (for example) 79 characters. This means that we have to write Markdown source with several new line characters even we are writing one paragraph. In order to overcome this incovenient situation, a comment formatting pakage pyls-cwrap has been prepared. You can install this package as pip install pyls-cwrap. In Atom, if you use ide-python, just press [Ctrl]+[Shift]+[C] (Windows, default setting), sequential comments are automatically formatted nicely.

5.4Source code

File3script.py

# # Standalone Script
# Using Atom's [Hydorgen](https://nteract.gitbooks.io/hydrogen/) package, you can
# execute any Python script codes within a fenced code block in a Markdown source. So
# you can edit your code verifying its execution results. But unfortunately (as long as
# I know), the entire Markdown source cannot be executed all at once as a standalone
# script and cannot be ran by Python interpreter. Pheasant connects between a pure
# Python script and a Markdown source. Actually, this page is written by a pure Python
# code.
# ## How to
# A basic idea is that Markdown cells and Python code cells generally appear
# alternately. We can write a Markdown cell with a successive comment lines. In order to
# be recognized as a Markdown cell, `#` must be at the begining of lines. But we can
# insert a blank line to make a paragraph.
# Normal Python code is treated as a code cell as you expect. A code cell can contain
# any comments as long as the comments don't start at the begining of line.
def add(x: int, y: int) -> int:
"""Add `x` and `y`."""
return x + y # a comment in a code cell.
def sub(x: int, y: int) -> int:
"""Substract `y` from `x`."""
return x - y # a comment in a code cell.
# When a comment starts at the begining of line after a code block, it divides the
# source into a code cell and a Markdown cell. This new Markdown cell will continue
# until next Python code appears.
# If you want to include a comment at the begining of line, you can write like this:
# ~~~python
# # !First comment in a code cell.
# a = 1
# ~~~
# becomes
# !First comment in a code cell.
a = 1
# Despite of a Markdown cell, you may want to devide successive codes into separate
# cells. This can be done by putting a special inline comment to define a cell. The
# comment pattern is `# -` or `# %%`. For example,
# ~~~python
# # * a markdown cell
# a, b, c = 1, 2, 3
# a
# # -
# b
# # %%
# c
# ~~~
# becomes
# * a markdown cell
a, b, c = 1, 2, 3
a
# -
b
# %%
c
# You can add options to a code block by adding them after a cell devider.
# ~~~python
# # %% hide
# d = 4
# # * Output: `d` is equal to {{d}}.
# ~~~
# Above python code is equivalent to the next Markdown source.
# ~~~
# ```python hide
# d = 4
# ```
# * Output: `d` is equal to {{d}}.
# ~~~
# Then you can hide the python code cell.
# %% hide
d = 4
# * Output: `d` is equal to {{d}}.
# ## Fenced code block in Python source
# You can write a fenced code block in a Python source as comment.
# ~~~python
# # ```python
# # print(1)
# # ```
# ~~~
# becomes:
# ```python
# print(1)
# ```
# And,
# ~~~python
# # ~~~
# # ```python
# # print(1)
# # ```
# # ~~~
# ~~~
# becomes:
# ~~~
# ```python
# print(1)
# ```
# ~~~
# ## A package for comment formatting
# In this scheme, we have to write many comments for Markdown cells. But a linter such
# as pycodestyle doesn't allow us to write a very long comment in one line longer than
# (for example) 79 characters. This means that we have to write Markdown source with
# several new line characters even we are writing one paragraph. In order to overcome
# this incovenient situation, a comment formatting pakage
# [`pyls-cwrap`](https://github.com/daizutabi/pyls-cwrap) has been prepared. You can
# install this package as `pip install pyls-cwrap`. In Atom, if you use
# [`ide-python`](https://atom.io/packages/ide-python), just press [Ctrl]+[Shift]+[C]
# (Windows, default setting), sequential comments are automatically formatted nicely.
# ## Source code
# #File script.py {%=script.py%}