doc/tutorials/base/conclusion.rst
author Laurent Peuch <cortex@worlddomination.be>
Mon, 22 Jul 2019 11:21:10 +0200
changeset 12696 eb83daa69495
parent 12378 9dcb5e4e705b
permissions -rw-r--r--
[cubicweb-ctl] respect sys.exit status code when aborting a command When exploring the stack of all calls to a cubicweb-ctl command, it has been discovered than on a KeyboardInterrupt and on a SystemExit exception the base class InstanceCommand (for commands that works on one instance) will always set the return code of cubicweb-ctl to 8: this mean that if another command do a `sys.exit(some_code)` the exit code will be ignored and overwritten by '8'. This behavior is not intuitive, apparently not documented and doesn't seems to have any justification. It also prevent commands from exciting with different return codes which could be a desired behavior in the situation of scripting.

.. -*- coding: utf-8 -*-

What's next?
------------

In this tutorial, we have seen that you can, right after the installation of
|cubicweb|, build a web application in a few minutes by defining a data model as
assembling cubes. You get a working application that you can then customize there
and there while keeping something that works. This is important in agile
development practices, you can right from the start of the project show things
to customer and so take the right decision early in the process.

The next steps will be to discover hooks, security, data sources, digging deeper
into view writing and interface customisation... Yet a lot of fun stuff to
discover! You will find more `tutorials and howtos`_ in the blog published on the
CubicWeb.org website.

.. _`tutorials and howtos`: ../../tutorials