50 |
50 |
51 * As a consequence of the replacement of the old looping tasks manager by a |
51 * As a consequence of the replacement of the old looping tasks manager by a |
52 scheduler, all cubicweb-ctl's "start" commands (i.e. ``start``, ``pyramid``, |
52 scheduler, all cubicweb-ctl's "start" commands (i.e. ``start``, ``pyramid``, |
53 ``wsgi``) do not start repository *looping tasks manager* anymore, nor do |
53 ``wsgi``) do not start repository *looping tasks manager* anymore, nor do |
54 they start the scheduler. Site administrators are thus expected to start |
54 they start the scheduler. Site administrators are thus expected to start |
55 this scheduler as a separate process. |
55 this scheduler as a separate process. Also, registering looping tasks (i.e. |
|
56 calling ``repo.looping_tasks()``) is a no-op when the repository has no |
|
57 scheduler set; a warning is issued in such cases. Application developers may |
|
58 rely on repository's ``has_scheduler`` method to determine if they should |
|
59 register a looping task or not. |
56 |
60 |
57 * In ``cubicweb.pyramid``, function ``make_cubicweb_application`` got renamed |
61 * In ``cubicweb.pyramid``, function ``make_cubicweb_application`` got renamed |
58 into ``config_from_cwconfig`` (950ce7d9f642). |
62 into ``config_from_cwconfig`` (950ce7d9f642). |
59 |
63 |
60 * Several cleanups in repository's session management have been conducted |
64 * Several cleanups in repository's session management have been conducted |