Add link to python-module-cookiecutter #1066
Conversation
Signed-off-by: Gaetan Semet <gaetan@xeberon.net>
Codecov Report
@@ Coverage Diff @@
## master #1066 +/- ##
======================================
Coverage 100% 100%
======================================
Files 18 18
Lines 781 781
======================================
Hits 781 781Continue to review full report at Codecov.
|
There was a problem hiding this comment.
Local tox test with merged #1181:
___________________________________________________________________________________________________________ summary ___________________________________________________________________________________________________________
py27: commands succeeded
py35: commands succeeded
py36: commands succeeded
py37: commands succeeded
ERROR: pypy: InterpreterNotFound: pypy
flake8: commands succeeded
Merge required to start #1179
|
We are no longer maintaining a list of templates inside README file and instead we use github topics feature. Please read https://github.com/cookiecutter/cookiecutter#a-pantry-full-of-cookiecutters and add the needed topics to your repository and people will be able to find your template. The most important one is We are also going to remove most of already listed templates from there, in order not avoid being biased. |
Hi,
This is the cookiecutter I use everytime I need to create a python module. I started using pipenv a months ago, and combined with PBR and a proper tooling (doing here around a Makefile), it applies very well to library and application use cases. It is generic, that is does not bootstrap the code, only the tooling and build system.
PBR and pipenv handles pretty much all key things:
To see its usages:
planned: backport the automatic release note generation using OpenStack's reno project.