Skip to main content

Yet another a project template tool for an organisation.

Project description Join the chat at


yehua /’jɛhwa/ is yet another a project template tool for an organisation. It creates a project skeleton, S from the default project template, T, of an organisation. moban, the other tool of moremoban organisation, keeps S in synchronisation with T forever. This use case is what we called: continuous templating.

Cookiecutter users

Yes, we now support cookiecutter templates. It has been requested since 2018 Europython. Simply there is tons of cookiecutter templates out there.

What you do is to replace ‘cookiecutter’ with ‘yh’:

$ pip install yehua[cookiecutter]
$ yh gh:audreyr/cookiecutter-pypackage

And what moremoban promise is, whenever your source template changes, you can synchronize them any time with another moremoban’s command ‘moban’:

$ moban

Yes, you need a separate command, which replaces your effort to synchronize the upstream templates all the time.

What’s different with Yehua

When the scope is a single project, yehua is no different to cookiecutter and PyScaffold. It will create a project skeleton from pypi-mobans, other templates such as cookiecutter templates, yehua mobans.

When the scope is all projects within an organisation, yehua helps tackle information fragmentation problem, because all new projects after its creation, are still in synchronisation with T. For example, removing python 2.7 test in your travis file, can be done either manually by hand or automatically via moban. What’s the difference? The latter is faster and typo-free option. Here is an example.

PyScaffold version 3 has rolled out ‘–update’ option, recognizing the organisational need of continous templating. Why do not yehua join PyScaffold? Well, moremoban organisation started with ‘–update’ at the start so our architecture and vision are closer to that of cookiecutter:

  1. we do not want to limit ourselves in pythonsphere. We wanted to serve all IT projects. In our mind, they are all about text templating.

  2. we split the tool and the templates, serving the previous statement. People can create npm package template and use yehua+moban for continuous templating. Here are a list of examples:


You can install yehua via pip:

$ pip install yehua

or clone it and install it:

$ git clone
$ cd yehua
$ python install

For offline usage, you need to get pypi-mobans-pkg installed:

$ pip install yehua[pypi-mobans]


$ pip install pypi-mobans-pkg


Simply type in and you are taken care of:

$ yh

It will use pypi-mobans-pkg by default and if it is not installed, it will install latest one. Then pypi-mobans-pkg takes over and will do [these]( for you:

  1. Consult you on your project static information which can update as many as you want to.

  2. Create the Python package folder structure

  3. Initialize the package as git project

You will simply need to commit it after you will have reviewed the generated files.


Let’s make a python command line utility using yehua. The command will be hello and it prints world.

Step 1 Let’s launch yehua


Step 2 Fill-in the meta data for your project


At the end, yehua generates a folder named ‘hello’, which contains [all necessary files](

Step 3 Start coding

In above animation, we write up the actual code in hello/

def main():

Why is it enough? yehua generates a command utility python and it has pre-wired to invoke hello.main.main() function. You can find it out in

Step 4 Install it

Now all is done. Let’s install it


You can now run hello at your command line.

Step 5 push to github

Suppose you are happy with everything. Please do the following to push it to your github:

$ git commit -am ":sparkle: initial commit"

Then create your project repository in github and do these to push it out:

$ git remote add origin
$ git push origin master

You can find the hello project on github.

Step 7 enable travis

The generated project already has .travis.yml file. What you will need to do is to register with if you have not done so. And then go to travis and activate your project.


The original problem I was trying to solve is: I would like to place common paragraphs in the documentation of my projects in a central place (pyexcel-mobans), and all projects could reference it dynamically so that when those common paragraphs get updated, the updates can be easily propagated to all relevant projects. The derived problem is: what can I do to a new project? I found myself doing a lot of copy-and-paste a lot, which lead to the creation of “yehua”. Later, John Vandenberg, an active member of coala, suggested extracting the generic sets of pyexcel-mobans to form pypi-mobans, so that a vanilla python package can be created. Why not cookiecutter? Well, I have not heard of it at the time of creation. But it turns out that this project started to pave the way to be the cookiecutter for organisations.

Why to choose “yehua”? Here is the little story behind the choice of name. And this music video would help bridge the cultural gap between you and me.


NEW BSD License

It embeds MIT licensed cutie from Hans Schülein. Please refer to LICENSE file for more details

3 contributors

In alphabetical order:

Change log

0.1.4 - 14.09.2020


  1. #53: parity with cookiecutter: support gh:audreyr/cookiecutter-pypackage

0.1.3 - 13.09.2020


  1. use pypi-mobans v0.1.0

  2. no longer, yehua has any template in itself.

0.1.2 - 26.08.2020


  1. support pypi-mobans v0.0.15.

  2. auto-generation of contributors

  3. github action for moban update and commits

  4. better isort action

0.1.1 - 29.05.2020


  1. #62: fix unwanted dependency for yh standalone use

0.1.0 - 19.05.2020


  1. python 2 support has been dropped


  1. -v is changed to do moban style verbose(-v, -vv, -vvv), for version, please use -V


  1. #37: cookiecutter support

  2. #38: non-verbose mode

  3. added moban update work flow

  4. python filesystem 2 support. yehua templates and cookiecutter templates can be in git, zip, s3, etc.

0.0.8 - 10-01-2020


  1. #30: ‘yh -h’ or ‘yh –help’ triggers help text

  2. #32: pypi-moban-pkg as installation extras

  3. enable auto github auto publishing

  4. generate mit license


  1. #35: better error message when the project name has been made a directory already

  2. updated moban dependency to v0.6.0

  3. updated yaml library to ruamel.yaml. PyYAML is out because only one yaml library is wanted in the organisation.

0.0.7 - 6/10/2019


  1. upgrade yehua to use pypi-mobans-pkg version 0.0.7

  2. generated project will have azure build pipeline, moban command stage in travis and local flake8 check

0.0.6 - 04/15/2019


  1. upgrade yehua to use pypi-mobans-pkg version 0.0.5

  2. generated project will have four new files: pipfile,, changelog.yml and Makefile

0.0.5 - 08/11/2018


  1. #6: provide Pipfile for pipenv

0.0.4 - 06/07/2018


  1. #11: keep up-to-date with pypi-mobans

0.0.3 - 24/02/2018


  1. To add all files to a git repo is being made optional. The action is specified in git-repo-files under post-moban section. This particular need arises when it is used to scaffold other type of projects such as npm.

0.0.2 - 15/10/2017


  1. Automatically inflate project meta data. One yehua command and typing a few questions are required before a complete project scaffolding

  2. Automatically obtain setupmobans repo for previous task.

  3. Automatically initialize package as git project and add all project files for the user to commit


  1. Built-in template files are off-loaded to setupmobans, which are more frequently updated.

0.0.1 - 02/07/2017

Project details

Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

yehua-0.1.4.tar.gz (43.5 kB view hashes)

Uploaded source

Built Distribution

yehua-0.1.4-py2.py3-none-any.whl (18.8 kB view hashes)

Uploaded py2 py3

Supported by

AWS AWS Cloud computing and Security Sponsor Datadog Datadog Monitoring Fastly Fastly CDN Google Google Download Analytics Microsoft Microsoft PSF Sponsor Pingdom Pingdom Monitoring Sentry Sentry Error logging StatusPage StatusPage Status page