python3.6にsphinxをインストール（Windows）

[この記事には改訂版があります](https://qiita.com/cosmos4701141/items/58b14e8a239dba578bbc)

python3.6をデフォルトのままインストールしたら、sphinxのインストールに失敗したのでメモ。

# 環境
Surface3 (Windows10 x64,メモリ4GB)

# python3.6のインストール
https://www.python.org/downloads/ から、python-3.6.1.exe をダウンロードする
起動すると C:\Program Files (x86) の下にインストールしようとするが、後で困ったのでインストール先を C:\Python36 に変更してインストールする

# Windows環境変数の追加
念のため、環境変数に、 C:\Python36\ C:\Python36\Scripts\ C:\Python36\Tools\Scripts C:\Python36\Lib\site-packages を追加する

# Sphinxのインストール
easy_install sphinx だけで完了する

# 動作テスト
mkdir test
cd test
sphinx-quichstart

	Welcome to the Sphinx 1.6.3 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: test
	> Author name(s): test

	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 []: 1.00
	> Project release [1.00]:

	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
	http://sphinx-doc.org/config.html#confval-language.
	> Project language [en]:

	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]:
	> intersphinx: link between Sphinx documentation of different projects (y/n) [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]:
	> ifconfig: conditional inclusion of content based on config values (y/n) [n]:
	> viewcode: include links to the source code of documented Python objects (y/n) [n]:
	> githubpages: create .nojekyll file to publish the document on GitHub pages (y/n) [n]:

	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.

make html

	Running Sphinx v1.6.3
	making output directory...
	loading pickled environment... not yet created
	building [mo]: targets for 0 po files that are out of date
	building [html]: targets for 1 source files that are out of date
	updating environment: 1 added, 0 changed, 0 removed
	reading sources... [100%] index
	looking for now-outdated files... none found
	pickling environment... done
	checking consistency... done
	preparing documents... done
	writing output... [100%] index
	generating indices... genindex
	writing additional pages... search
	copying static files... done
	copying extra files... done
	dumping search index in English (code: en) ... done
	dumping object inventory... done
	build succeeded.

	Build finished. The HTML pages are in _build\html.