* Use f-strings instead of .format()
* Code block language marker fixes
* Make example code blocks syntactically valid Python
* Run all python code blocks through black
https://github.com/scop/misc/blob/master/black_markdown.py
* Add some missing code block language markers
* Use shell language consistently to mark shell code blocks
* Undo folding of some example dicts
* Remove outdated OrderedDict comments per Python 3.7, replace with plain dict
I was following the instructions, but they don't work at all for Windows. Issues fixed:
* The old command would use python3.6, but home assistant requires 3.7
* Picks up the change in https://github.com/home-assistant/developers.home-assistant/pull/335 for the Windows section.
* Explicitly use 3.7 when setting up the venv, since on some systems `python3` points to 3.6, not 3.7
* Dev 0.89 needs some extra tox dependencies to run
This is based on an issue as seen here https://github.com/home-assistant/home-assistant/issues/22068.
* Update development-environment.md based on C.R.
Included the changes needed to run on Windows and Mac. The extra command for OS X is not tested (I am not able to work with OS X).
* Update development_environment.md
* Config folder location clarification
While this was documented elsewhere in the docs, this is the first thing I was looking for after invoking the dev environment and spent an inordinate amount of time tracking it down.
* link to user docs for clarification
link to user docs to clarify location of config files
When running `tox` on OSX as instructed at https://developers.home-assistant.io/docs/en/development_testing.html an error is received stating `error: [Errno 2] No such file or directory: 'autoconf': 'autoconf'`.
By installing `autoconf` via `homebrew`, this error goes away, and the `tox` tests pass. Telling OSX developers to install `autoconf` at this point in the development environment setup procedure (rather than calling it out on the testing page) seemed to make sense to me.
