emzed Apps

emzed supports the creation of extensions, which we call emzed packages or emzed apps. In order to implement such a package we provide some helper functions which we describe below. You should be familiar with implementing Python modules before trying to create your own emzed package.

Those extensions are available after installation and starting a new Python interpreter in name spaces emzed.ext and/or emzed.app. The first is intended to provide new functions as building blocks for new workflows, the latter houses complete workflows aka emzed apps.

Create your own emzed project

Before you start on your own emzed project, make sure that the emzed project folder is configured:

import emzed.config   # not needed if working in workbench

All project related commands are in the module emzed.project and have shortcuts in IPython shell staring with three underscores ___ which helps to facilitate completion with TAB when working on projects.

We demonstate the creation of a new package demo_package. To start we enter one of the following two commands:

___init_new_project()                # asks for name
___init_new_project("demo_package")  # only a-z, 0-9 and '_' are allowed

Outside the workbench (we assume that you imported emzed already) you can use:

emezd.project.init()                 # asks for name

This sets up a folder scaffold for your project inside the configured emzed project folder and changes the current working directory to it.

You should edit these files:

  • LICENSE: at least edit year and name of author and give a one line description in the marked places.

  • README is the place to describe your project.

  • setup.py is the configuration file which is needed for installation and distribution of your package:

    • If you set IS_EXTENSION to True your package can be imported in emzed as emzed.ext.demo_package.
    • If you set APP_MAIN your extension is installed below emzed.app and can be started

    as emzed.app.demo_package(). The value of APP_MAIN hints to the Python file and function in this file which is started in the end.

    • You should fill out author information AUTHOR, AUTHOR_EMAIL and AUTHOR_URL with

    your name, email adress and website.

    • DESCRIPTION and LONG_DESCRIPTION will be shown as information on Pythons Package

    Index if you upload your packae.

    • Check that the value of LICENSE fits your needs.

Further the following folders were created below the project folder:

  • demo_package for the Python modules of your package. Study the files inside this folder in order to understand how to setup these files. If you are new to Python you first should learn about implementation of Python modules and packages.
  • tests for unit tests. It is important that the files in this folder and the test functions in these files start with test_. You find demo files there.

Working on your project

The IPython prompt in the workbench console shows the active project. You can change or set this using two alternative abbreviations:

___start_work_on()                # asks for name

Outside the workbench you can use one of:


Starting emzed.workbench the last package you worked on is activated by default.

Writing and running tests

As said tests contains should contain tests for your package. It is important that the files in this folder and the test functions in these files start with test_. You find demo files there.

To run the tests start:




Distributing your package





create a file with extension .whl in your project folder. You can send this file to colleagues which can install it using:

___install_wheel()                                   # asks for whl file
___install_wheel("/tmp/downloads/demo_package.whl")  # you can also provide a path


emzed.project.install_wheel()                        # asks for whl file

If you followed the steps above for creation the package demo_package, building the wheel and installing it afterwards, you can test now:

>>> import emzed
>>> print emzed.ext.demo_package.hello()
hello from demo_package
>>> emzed.app.demo_package()

You should inspect the files in our project folder for demo_package to see how the extension and the app are implemented.