[pyramid] Let logging be configured through .ini file We do not initialize logging in CubicWebPyramidConfiguration thus preventing logging to be started with cubicweb's configuration. On the other hand, any logging configuration defined in ``development.ini`` file will be loaded by whatever start the instance using this file (i.e. pserve, gunicorn, etc.). The benefit is that logging can now be configured per "qualified name" in this file (i.e. one can easily set the DEBUG level for the application cube while keeping all dependencies' level to WARNING). In the development.ini template, we add logger configurations for "logilab" and "cubicweb" qualified names (along with those of the application cube).

     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