[Python] SphixでMarkdownを使ってみたけど、イマイチだった

Facebook にシェア
Pocket
LINEで送る
このエントリーを Google ブックマーク に追加

まぁあるとは思ったけど調べていなかった。
そして、イマイチだったので保留。

[amazonjs asin=”B00XZTYMG6″ locale=”JP” title=”Pythonプロフェッショナルプログラミング 第2版”]

イマイチだった点

使うのを保留した理由として、 「テーブルが対応してなかった」

前提

ここあたりを参考にして、Pyenv環境を構築。執筆時はPython3.5.1をインストール。

Macにpyenvをインストール

Pythonのバージョンが3.5.1になってるか確認。

[python] $ python –version
Python 3.5.1
[/shell]

<br />
<br />
## Sphixをインストール

仮想環境を構築し、Sphinxとマークダウンを使うためのrecommonmarkをインストールする。
(sphinx_bootstrap_themeは後述する部分で使うため、念のため)

[shell] mkdir ~/.venv
pyenv ~/.venv/sphinx
source ~/.venv/sphinx/bin/activate
pip install –upgrade pip
pip install sphinx sphinx_bootstrap_theme recommonmark
[/shell]

<br />

## プロジェクトを作成

[shell] $ cd ~/
$ mkdir ./markdown_test
$ cd markdown_test
$ sphinx-quickstart

#諸々の質問に答える。あとで修正可能。

Welcome to the Sphinx 1.4.4 quickstart utility.

Please enter values for the following settings (just press Enter to
accept a default value, if one is given in brackets).

Enter the root path for documentation.
> Root path for the documentation [.]:

You have two options for placing the build directory for Sphinx output.
Either, you use a directory "_build" within the root path, or you separate
"source" and "build" directories within the root path.
> Separate source and build directories (y/n) [n]:

Inside the root directory, two more directories will be created; "_templates"
for custom HTML templates and "_static" for custom stylesheets and other static
files. You can enter another prefix (such as ".") to replace the underscore.
> Name prefix for templates and static dir [_]:

The project name will occur in several places in the built documentation.
> Project name:
* Please enter some text.
> Project name:
[Interrupted.] (sphinx) umentu-no-MacBook-Pro% sphinx-quickstart
Welcome to the Sphinx 1.4.4 quickstart utility.

Please enter values for the following settings (just press Enter to
accept a default value, if one is given in brackets).

Enter the root path for documentation.
> Root path for the documentation [.]:

You have two options for placing the build directory for Sphinx output.
Either, you use a directory "_build" within the root path, or you separate
"source" and "build" directories within the root path.
> Separate source and build directories (y/n) [n]:

Inside the root directory, two more directories will be created; "_templates"
for custom HTML templates and "_static" for custom stylesheets and other static
files. You can enter another prefix (such as ".") to replace the underscore.
> Name prefix for templates and static dir [_]:

The project name will occur in several places in the built documentation.
> Project name: markdown_test
> Author name(s): umentu

Sphinx has the notion of a "version" and a "release" for the
software. Each version can have multiple releases. For example, for
Python the version is something like 2.5 or 3.0, while the release is
something like 2.5.1 or 3.0a1. If you don’t need this dual structure,
just set both to the same value.
> Project version: 0.0.1
> Project release [0.0.1]:

If the documents are to be written in a language other than English,
you can select a language here by its language code. Sphinx will then
translate text that it generates into that language.

For a list of supported codes, see
https://sphinx-doc.org/config.html#confval-language.
> Project language [en]: ja

The file name suffix for source files. Commonly, this is either ".txt"
or ".rst". Only files with this suffix are considered documents.
> Source file suffix [.rst]:

One document is special in that it is considered the top node of the
"contents tree", that is, it is the root of the hierarchical structure
of the documents. Normally, this is "index", but if your "index"
document is a custom template, you can also set this to another filename.
> Name of your master document (without suffix) [index]:

Sphinx can also add configuration for epub output:
> Do you want to use the epub builder (y/n) [n]:

Please indicate if you want to use one of the following Sphinx extensions:
> autodoc: automatically insert docstrings from modules (y/n) [n]:
> doctest: automatically test code snippets in doctest blocks (y/n) [n]:
) [n]: sphinx: link between Sphinx documentation of different projects (y/n)
: todo: write "todo" entries that can be shown or hidden on build (y/n) [n]:
> coverage: checks for documentation coverage (y/n) [n]:
> imgmath: include math, rendered as PNG or SVG images (y/n) [n]:
> mathjax: include math, rendered in the browser by MathJax (y/n) [n]:
n]: config: conditional inclusion of content based on config values (y/n) [n
y/n) [n]: : include links to the source code of documented Python objects (y
s (y/n) [n]: : create .nojekyll file to publish the document on GitHub pages

A Makefile and a Windows command file can be generated for you so that you
only have to run e.g. `make html’ instead of invoking sphinx-build
directly.
> Create Makefile? (y/n) [y]:
> Create Windows command file? (y/n) [y]:

Creating file ./conf.py.
Creating file ./index.rst.
Creating file ./Makefile.
Creating file ./make.bat.

Finished: An initial directory structure has been created.

You should now populate your master file ./index.rst and create other documentation
source files. Use the Makefile to build the docs, like so:
make builder
where "builder" is one of the supported builders, e.g. html, latex or linkcheck.
[/shell] <br />
中身を確認する。
[shell] $ ls
Makefile _static conf.py make.bat
_build _templates index.rst
[/shell]

<br />
<br />
## conf.pyを編集する

recommonmarkを使うために、conf.pyを編集する。

[python]

#15行目くらい
import sys
import os

# 追記
from recommonmark.parser import CommonMarkParser

# ・・・・・

# ファイル末尾に追記

source_parsers = {
‘.md’: CommonMarkParser,
}
source_suffix = [‘.rst’, ‘.md’] [/python]

Markdownを使ってみる

~/markdown_test 配下に markdown.md ファイルを作成して、以下を記述。

[shell title=”markdown.md”] # Test
> aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
> vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv
> dddddddddddddddddddddddddddddddddddddddddddd

## Test01
### Test001

| aa | vv | bb |
| — | — | — |
| ss | dd | ff |
[/shell]

index.rst に markdown.mdの存在を知らせる。

[shell title=”index.md”] .. markdown_test documentation master file, created by
sphinx-quickstart on Sat Jul 9 16:09:06 2016.
You can adapt this file completely to your liking, but it should at least
contain the root `toctree` directive.

Welcome to markdown_test’s documentation!
=========================================

Contents:

.. toctree::
:maxdepth: 2

markdown

Indices and tables
==================

* :ref:`genindex`
* :ref:`modindex`
* :ref:`search`
[/shell]

コンパイルする。

[shell] cd ~/markdown_test/
make html
[/shell]

~/markdown_test/_build/html/markdown.htmlをブラウザで開いてみる。

スクリーンショット 2016-07-09 16.46.44

テーブルが対応していなさそう。

Related posts

コメントを残す