Quick and Dirty Installation¶
To get started with Morepath right away, first create a Python 3.5 virtualenv:
$ virtualenv morepath_env $ source morepath_env/bin/activate
Now install Morepath into it:
$ pip install morepath
You can now use the virtual env’s Python to run any code that uses Morepath:
$ python quickstart.py
See Quickstart for information on how to get started with
Morepath itself, including an example of
Creating a Morepath Project Manually¶
When you develop a web application it’s a good idea to use standard
Python project organization practices. Organizing your Project
has some recommendations on how to do this with Morepath. Relevant in
particular is the contents of
setup.py, which depends on Morepath
and also sets up an entry point to start the web server.
With pip and a virtualenv called
morepath_env, you can do this in
your project’s root directory:
$ pip install --editable .
You can now run the application like this (if you called the console
Buildout is more involved than pip, but can also do a lot more for you automatically and repeatedly.
buildout.cfg file containing this:
[buildout] develop = . parts = scripts devpython versions = versions [versions] venusian = 1.0a8 morepath = 0.1 reg = 0.6 [scripts] recipe = zc.recipe.egg:scripts eggs = myproject pytest [devpython] recipe = zc.recipe.egg interpreter = devpython eggs = myproject flake8
This describes how to install our project for development. Change
myproject to the name your project has in
Place a buildout bootstrap.py in your project’s root directory.
The first time you create or check out a project you need to bootstrap
the buildout. You can do this using the
bootstrap.py script. Do
this from a virtualenv:
$ /path/to/morepath_env/bin/python bootstrap.py
You only need to do this once. After that you can run:
each time you want to redo the installation after you change the buildout config. It’s safe to run this when nothing has really changed too.
Once you’ve run buildout, you can start your application. If it’s
myproject-start in the entry point in
setup.py, you can
run it like this:
What’s going on with buildout?¶
What’s going on? What else did that
buildout.cfg do for us?
develop line tells which directories to look in for Python
projects (with a
setup.py). In this case only the local project
. is one. But if you also have the checkout of another
project that you depend on (maybe a development version of Morepath
itself), you can add that directory to the
parts tells buildout what to configure; they are described in
[devpython] sections later.
versions=versions tells buildout to lock down version
numbers according to the
[scripts] section installs your web application as a script in
bin subdirectory of your project, according to the
console_scripts entry point in your project’s
myproject-start, then you can start it like this:
This will start a HTTP server for your project.
The buildout also has installed pytest so you can run your project’s tests automatically:
(if your Python package is in
Now as to some optional extras. The
[devpython] section installs a
Python interpreter which can import exactly what your project can
import. It assumes your project is called
myproject in its
setup.py; change the name to match your project. You can start it
You’ll get the usual Python console
>>>. This is useful for
testing your project’s imports and API manually.
It also installs the flake8 tool which runs pep 8 checks and pyflakes automatically. You can run it against your project by writing:
$ bin/flake8 myproject
myproject is your project’s source code directory.
Depending on Morepath development versions¶
If you like being on the cutting edge and want to depend on the latest Morepath and Reg development versions always, we recommend you use buildout with the mr.developer extension for your project. You can see how in this buildout.cfg.
You can also install these using pip (in a virtualenv). Here’s how:
$ pip install git+git://github.com/morepath/reg.git@master $ pip install git+git://github.com/morepath/morepath.git@master