Moved examples pacakge out from eventsourcing package into repo root …

…folder.

docs/topics/domain.rst

@@ -1331,7 +1331,8 @@ for an example of this style of implementing aggregate projector functions.
 ..
     #include-when-testing
 ..
-    from eventsourcing.examples.cargoshipping.domainmodel import Location, singledispatchmethod
+    from eventsourcing.dispatch import singledispatchmethod
+    from examples.cargoshipping.domainmodel import Location
 
 .. code-block:: python
 

docs/topics/examples/aggregate1.rst

@@ -16,18 +16,18 @@ Python object class.
 Domain model
 ------------
 
-.. literalinclude:: ../../../eventsourcing/examples/aggregate1/domainmodel.py
+.. literalinclude:: ../../../examples/aggregate1/domainmodel.py
 
 
 Application
 -----------
 
 
-.. literalinclude:: ../../../eventsourcing/examples/aggregate1/application.py
+.. literalinclude:: ../../../examples/aggregate1/application.py
 
 
 Test case
 ---------
 
 
-.. literalinclude:: ../../../eventsourcing/examples/aggregate1/test_application.py
+.. literalinclude:: ../../../examples/aggregate1/test_application.py

docs/topics/examples/aggregate2.rst

@@ -19,18 +19,18 @@ class as if it were a normal Python object class.
 Domain model
 ------------
 
-.. literalinclude:: ../../../eventsourcing/examples/aggregate2/domainmodel.py
+.. literalinclude:: ../../../examples/aggregate2/domainmodel.py
 
 
 Application
 -----------
 
 
-.. literalinclude:: ../../../eventsourcing/examples/aggregate2/application.py
+.. literalinclude:: ../../../examples/aggregate2/application.py
 
 
 Test case
 ---------
 
 
-.. literalinclude:: ../../../eventsourcing/examples/aggregate2/test_application.py
+.. literalinclude:: ../../../examples/aggregate2/test_application.py

docs/topics/examples/aggregate3.rst

@@ -21,18 +21,18 @@ class as if it were a normal Python object class, albeit the aggregate class met
 Domain model
 ------------
 
-.. literalinclude:: ../../../eventsourcing/examples/aggregate3/domainmodel.py
+.. literalinclude:: ../../../examples/aggregate3/domainmodel.py
 
 
 Application
 -----------
 
 
-.. literalinclude:: ../../../eventsourcing/examples/aggregate3/application.py
+.. literalinclude:: ../../../examples/aggregate3/application.py
 
 
 Test case
 ---------
 
 
-.. literalinclude:: ../../../eventsourcing/examples/aggregate3/test_application.py
+.. literalinclude:: ../../../examples/aggregate3/test_application.py

docs/topics/examples/aggregate4.rst

@@ -26,18 +26,18 @@ repository and when taking snapshots.
 Domain model
 ------------
 
-.. literalinclude:: ../../../eventsourcing/examples/aggregate4/domainmodel.py
+.. literalinclude:: ../../../examples/aggregate4/domainmodel.py
 
 
 Application
 -----------
 
 
-.. literalinclude:: ../../../eventsourcing/examples/aggregate4/application.py
+.. literalinclude:: ../../../examples/aggregate4/application.py
 
 
 Test case
 ---------
 
 
-.. literalinclude:: ../../../eventsourcing/examples/aggregate4/test_application.py
+.. literalinclude:: ../../../examples/aggregate4/test_application.py

docs/topics/examples/aggregate5.rst

@@ -27,18 +27,18 @@ supplied when getting an aggregate from the repository and when taking snapshots
 Domain model
 ------------
 
-.. literalinclude:: ../../../eventsourcing/examples/aggregate5/domainmodel.py
+.. literalinclude:: ../../../examples/aggregate5/domainmodel.py
 
 
 Application
 -----------
 
 
-.. literalinclude:: ../../../eventsourcing/examples/aggregate5/application.py
+.. literalinclude:: ../../../examples/aggregate5/application.py
 
 
 Test case
 ---------
 
 
-.. literalinclude:: ../../../eventsourcing/examples/aggregate5/test_application.py
+.. literalinclude:: ../../../examples/aggregate5/test_application.py

docs/topics/examples/aggregate6.rst

@@ -20,18 +20,18 @@ repository and when taking snapshots.
 Domain model
 ------------
 
-.. literalinclude:: ../../../eventsourcing/examples/aggregate6/domainmodel.py
+.. literalinclude:: ../../../examples/aggregate6/domainmodel.py
 
 
 Application
 -----------
 
 
-.. literalinclude:: ../../../eventsourcing/examples/aggregate6/application.py
+.. literalinclude:: ../../../examples/aggregate6/application.py
 
 
 Test case
 ---------
 
 
-.. literalinclude:: ../../../eventsourcing/examples/aggregate6/test_application.py
+.. literalinclude:: ../../../examples/aggregate6/test_application.py

docs/topics/examples/aggregate7.rst

@@ -31,25 +31,25 @@ aggregate events and from recorded snapshots.
 Domain model
 ------------
 
-.. literalinclude:: ../../../eventsourcing/examples/aggregate7/domainmodel.py
+.. literalinclude:: ../../../examples/aggregate7/domainmodel.py
 
 
 Application
 -----------
 
 
-.. literalinclude:: ../../../eventsourcing/examples/aggregate7/application.py
+.. literalinclude:: ../../../examples/aggregate7/application.py
 
 
 Persistence
 -----------
 
 
-.. literalinclude:: ../../../eventsourcing/examples/aggregate7/persistence.py
+.. literalinclude:: ../../../examples/aggregate7/persistence.py
 
 
 Test case
 ---------
 
 
-.. literalinclude:: ../../../eventsourcing/examples/aggregate7/test_application.py
+.. literalinclude:: ../../../examples/aggregate7/test_application.py

docs/topics/examples/aggregate8.rst

@@ -30,25 +30,25 @@ aggregate events and from recorded snapshots.
 Domain model
 ------------
 
-.. literalinclude:: ../../../eventsourcing/examples/aggregate8/domainmodel.py
+.. literalinclude:: ../../../examples/aggregate8/domainmodel.py
 
 
 Application
 -----------
 
 
-.. literalinclude:: ../../../eventsourcing/examples/aggregate8/application.py
+.. literalinclude:: ../../../examples/aggregate8/application.py
 
 
 Persistence
 -----------
 
 
-.. literalinclude:: ../../../eventsourcing/examples/aggregate8/persistence.py
+.. literalinclude:: ../../../examples/aggregate8/persistence.py
 
 
 Test case
 ---------
 
 
-.. literalinclude:: ../../../eventsourcing/examples/aggregate8/test_application.py
+.. literalinclude:: ../../../examples/aggregate8/test_application.py

docs/topics/examples/bank-accounts.rst

@@ -14,7 +14,7 @@ closed. Deposits and withdraws can be made on open accounts. Transfers can be
 made between open accounts, if there are sufficient funds on the debited account.
 All actions are atomic, including transfers between accounts.
 
-.. literalinclude:: ../../../eventsourcing/examples/bankaccounts/application.py
+.. literalinclude:: ../../../examples/bankaccounts/application.py
 
 
 Domain model
@@ -29,7 +29,7 @@ the account has been closed. Debits are not allowed if the
 balance would go below the overdraft limit. The overdraft
 limit can be adjusted.
 
-.. literalinclude:: ../../../eventsourcing/examples/bankaccounts/domainmodel.py
+.. literalinclude:: ../../../examples/bankaccounts/domainmodel.py
 
 
 Test case
@@ -40,4 +40,4 @@ might be used, the test runs through a scenario that
 exercises all the methods of the application in one
 test method.
 
-.. literalinclude:: ../../../eventsourcing/examples/bankaccounts/test.py
+.. literalinclude:: ../../../examples/bankaccounts/test.py

docs/topics/examples/cargo-shipping.rst

@@ -28,7 +28,7 @@ to be registered.
 The ``Booking`` application defines and registers custom transcodings for the
 custom value objects that are defined and used in the domain model.
 
-.. literalinclude:: ../../../eventsourcing/examples/cargoshipping/application.py
+.. literalinclude:: ../../../examples/cargoshipping/application.py
 
 Domain model
 ------------
@@ -48,7 +48,7 @@ For the purpose of simplicity in this example, a fixed collection of routes betw
 locations are also defined, but in practice these would be editable and could be
 also modelled as event-sourced aggregates.
 
-.. literalinclude:: ../../../eventsourcing/examples/cargoshipping/domainmodel.py
+.. literalinclude:: ../../../examples/cargoshipping/domainmodel.py
 
 
 Interface
@@ -66,7 +66,7 @@ the purposes of testing, we need to simulate the user selecting a preferred
 itinerary from a list, which we do by picking the first in the list of presented
 options using the ``select_preferred_itinerary()`` function.
 
-.. literalinclude:: ../../../eventsourcing/examples/cargoshipping/interface.py
+.. literalinclude:: ../../../examples/cargoshipping/interface.py
 
 
 Test case
@@ -80,4 +80,4 @@ handling events as it is shipped around the world, recovering by
 assigning a new route after the cargo was unloaded in the wrong place,
 until finally the cargo is claimed at its correct destination.
 
-.. literalinclude:: ../../../eventsourcing/examples/cargoshipping/test.py
+.. literalinclude:: ../../../examples/cargoshipping/test.py

docs/topics/examples/content-management-system.rst

@@ -45,7 +45,7 @@ system module guarantees that the diffs will always be applied in the correct or
 this guarantee, the projection could become inconsistent, with the consequence that the diffs
 will fail to be applied.
 
-.. literalinclude:: ../../../eventsourcing/examples/contentmanagementsystem/application.py
+.. literalinclude:: ../../../examples/contentmanagementsystem/application.py
 
 System
 ------
@@ -54,7 +54,7 @@ A :class:`~eventsourcing.system.System` of applications is defined, in which the
 ``SearchIndexApplication`` follows the ``ContentManagementApplication``. This system
 can then be used in any :class:`~eventsourcing.system.Runner`.
 
-.. literalinclude:: ../../../eventsourcing/examples/contentmanagementsystem/system.py
+.. literalinclude:: ../../../examples/contentmanagementsystem/system.py
 
 PostgreSQL
 ----------
@@ -65,7 +65,7 @@ The PostgreSQL :class:`~eventsourcing.postgres.Factory` class is extended to inv
 in a custom persistence module so that it can be used by the ``SearchIndexApplication``.
 
 
-.. literalinclude:: ../../../eventsourcing/examples/contentmanagementsystem/postgres.py
+.. literalinclude:: ../../../examples/contentmanagementsystem/postgres.py
 
 SQLite
 ------
@@ -75,7 +75,7 @@ is used to define a custom :class:`~eventsourcing.persistence.ProcessRecorder` f
 The SQLite :class:`~eventsourcing.sqlite.Factory` class is extended to involve this custom recorder
 in a custom persistence module so that it can be used by the ``SearchIndexApplication``.
 
-.. literalinclude:: ../../../eventsourcing/examples/contentmanagementsystem/sqlite.py
+.. literalinclude:: ../../../examples/contentmanagementsystem/sqlite.py
 
 
 Test case
@@ -86,4 +86,4 @@ and 'minerals'. Content is added to the pages. The content is searched with vari
 the search results are checked. The test is executed twice, once with the application configured
 for both PostgreSQL, and once for SQLite.
 
-.. literalinclude:: ../../../eventsourcing/examples/contentmanagementsystem/test_system.py
+.. literalinclude:: ../../../examples/contentmanagementsystem/test_system.py

docs/topics/examples/content-management.rst

@@ -39,7 +39,7 @@ Please note, although the domain model (see below) involves a ``user_id`` event
 none of the application command methods mention a ``user_id`` argument. Instead the value
 is set in a context variable by callers of the application command methods (see the test below).
 
-.. literalinclude:: ../../../eventsourcing/examples/contentmanagement/application.py
+.. literalinclude:: ../../../examples/contentmanagement/application.py
 
 
 Domain model
@@ -67,13 +67,13 @@ pages of text, with editable titles, and with editable "slugs" that can be used
 
 A ``PageLogged`` event is also defined, and used to define a "page log" in the application.
 
-.. literalinclude:: ../../../eventsourcing/examples/contentmanagement/domainmodel.py
+.. literalinclude:: ../../../examples/contentmanagement/domainmodel.py
 
 
 The ``create_diff()`` and ``apply_patch()`` functions use the Unix command line
 tools ``patch`` and ``diff``.
 
-.. literalinclude:: ../../../eventsourcing/examples/contentmanagement/utils.py
+.. literalinclude:: ../../../examples/contentmanagement/utils.py
 
 
 Test case
@@ -83,4 +83,4 @@ The test case below sets a user ID in the context variable. A page is created
 and updated in various ways. At the end, all the page events are checked to
 make sure they all have the user ID that was set in the context variable.
 
-.. literalinclude:: ../../../eventsourcing/examples/contentmanagement/test.py
+.. literalinclude:: ../../../examples/contentmanagement/test.py

docs/topics/examples/searchable-content.rst

@@ -18,7 +18,7 @@ parameters ``insert_pages`` and ``update_pages``. It also introduces a ``search(
 expects a ``query`` argument and returns a list of pages. The application's recorders are expected
 to be receptive to these variable keyword parameters and to support the ``search_pages()`` function.
 
-.. literalinclude:: ../../../eventsourcing/examples/searchablecontent/application.py
+.. literalinclude:: ../../../examples/searchablecontent/application.py
 
 
 Persistence
@@ -29,7 +29,7 @@ defining abstract methods to search and select pages. These methods will be impl
 for both PostgreSQL and SQLite, which will also create custom tables for page content with
 a full text search indexes.
 
-.. literalinclude:: ../../../eventsourcing/examples/searchablecontent/persistence.py
+.. literalinclude:: ../../../examples/searchablecontent/persistence.py
 
 The ``_insert_events()`` methods of the PostgreSQL and SQLite recorders are extended, so that
 rows are inserted and updated, according to the information passed down from the application
@@ -43,7 +43,7 @@ The PostgreSQL recorder uses a GIN index and the ``websearch_to_tsquery()`` func
 The PostgreSQL :class:`~eventsourcing.postgres.Factory` class is extended to involve this custom recorder
 in a custom PostgreSQL persistence module so that it can be used by the ``ContentManagementApplication``.
 
-.. literalinclude:: ../../../eventsourcing/examples/searchablecontent/postgres.py
+.. literalinclude:: ../../../examples/searchablecontent/postgres.py
 
 SQLite
 ------
@@ -52,7 +52,7 @@ The SQLite recorder uses a virtual table and the ``MATCH`` operator.
 The SQLite :class:`~eventsourcing.sqlite.Factory` class is extended to involve this custom recorder
 in a custom SQLite persistence module so that it can be used by the ``ContentManagementApplication``.
 
-.. literalinclude:: ../../../eventsourcing/examples/searchablecontent/sqlite.py
+.. literalinclude:: ../../../examples/searchablecontent/sqlite.py
 
 
 Test case
@@ -64,4 +64,4 @@ content is searched with various queries and the search results are checked. The
 test case is executed twice, once with the PostgreSQL persistence module, and once with the
 SQLite persistence module.
 
-.. literalinclude:: ../../../eventsourcing/examples/searchablecontent/test_application.py
+.. literalinclude:: ../../../examples/searchablecontent/test_application.py