[server] introduce a scheduler class to run repository "looping tasks" We just use the sched module from the standard library and introduce a tiny Python2/3 compatibility layer (more for convenience actually). The "looping" aspect of tasks (previously in LoopTask class) is re-implemeted as a `schedule_periodic_task` function. This is a reasonably thin layer as compared to LoopTask/TasksManager classes. Only the "restart" aspect of LoopTask is no longer present as I'm not sure it's worth keeping. The advantage of using this (in addition to eventually dropping our custom code) is that this scheduler class provides a `run` method that blocks the process while running tasks in its queue. So we can rely on this to have a 'scheduler' ctl command (see forthcoming patch) that would only run "looping tasks" without having to implement the "blocking" aspect ourself. Related to #17057223.

     1

[MASTER]

     2

load-plugins=cubicweb.pylintext

     3

ignore=__pkginfo__

     4

     5

[MESSAGES CONTROL]

     6

disable = too-many-ancestors,too-many-instance-attributes,too-many-public-methods,

     7

      too-few-public-methods,too-many-arguments,import-error

     8

     9

[BASIC]

    10

function-rgx = [a-z_][a-z0-9_]{2,35}$

    11

good-names=w,_

    12

    13

[TYPECHECK]

    14

generated-members=debug,info,notice,warning,error,critical,exception

    15

    16

[CLASSES]

    17

exclude-protected=_cw,_cnx,

    18

      # namedtuple public API.

    19

      _asdict,_fields,_replace,_source,_make

    20

    21

    22

[FORMAT]

    23

max-line-length=100

    24

max-module-lines=2000