Python boilerplate

[Fernando Felix do Nascimento Junior]

@all

I released version 1.0.0 with a tiny glossary and explanation of each file in the boilerplate.

@Chris

I made the boilerplate with intent that everyone can understand, download and use quickly. So, I didn't put extra dependence like cookiecutter (that depends jinja, that depends markupsafe) to **just** replace fields and then run the project.

I also preferred to use .md instead .rst because it's more clean in my opinion and used by default in platforms like GitHub and Stackoverflow. See mkdocs to generate documentation with markdown.

In same way, I choose pytest because the default test framework is verbose and its CamelCase sux.

About entry_points maybe I'll consider it too, but I didn't understand why packages are best than modules... both can be reusable and not every project needs packages.

I looked your release shell script. It's very nice. In Flask GitHub repository has a pretty nice too. See it ~scripts/make-release.py.


Thanks,