pylintrc
author Sylvain Thénault <sylvain.thenault@logilab.fr>
Thu, 01 Aug 2013 13:55:11 +0200
branchstable
changeset 9213 312062f53981
parent 0 b97547f5f1fa
child 11216 efecb78bf929
permissions -rw-r--r--
[inlined form field] fix regression introduced in 3.16.4/570208f74a84. Closes #3064653 In the above changeset, we changed ordered entities to be edited according to mandatory inlined constraints, though this leads to unpredictable order in cases where there are no constraint. This leads to case where inlined relation field may think there is no value related to a mandatory relation, while this is simply because there is a value specified but to an entity that will be created later (together with the relation). To fix this, we've to use the fact that the RelationField.process_form_value return None in cases where there is some entity to be created, while an empty set when there are no linked entity. The new no_value() method allows to differentiate between those different notion of 'no-value'.

[MESSAGES CONTROL]
disable-msg = C0301

[VARIABLES]
# Enable / disable this checker
enable-variables = yes
additional-builtins = _, display_name

[BASIC]
required-attributes=
attr-rgx = (w|[a-z_][a-z0-9_]{2,30})
variable-rgx = (w|[a-z_][a-z0-9_]{2,30})$
argument-rgx = (w|[a-z_][a-z0-9_]{2,30})$

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