Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.python > #105317

Re: Python boilerplate

Newsgroups comp.lang.python
Date 2016-03-20 16:36 -0700
References <17c30829-4d9e-49ab-ad93-acc217a55aee@googlegroups.com> <mailman.390.1458395668.12893.python-list@python.org>
Message-ID <61c94e82-8bcc-4855-a856-468bcadfe486@googlegroups.com> (permalink)
Subject Re: Python boilerplate
From Fernando Felix do Nascimento Junior <fernandojr.ifcg@live.com>

Show all headers | View raw


@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,

Back to comp.lang.python | Previous | NextPrevious in thread | Next in thread | Find similar | Unroll thread


Thread

Python boilerplate Fernando Felix do Nascimento Junior <fernandojr.ifcg@live.com> - 2016-03-19 05:43 -0700
  Re: Python boilerplate Fernando Felix do Nascimento Junior <fernandojr.ifcg@live.com> - 2016-03-20 16:36 -0700
    Re: Python boilerplate Chris Warrick <kwpolska@gmail.com> - 2016-03-21 17:03 +0100
  Re: Python boilerplate Sam <python@net153.net> - 2016-03-19 12:28 -0500

csiph-web