pylintrc
author Adrien Di Mascio <Adrien.DiMascio@logilab.fr>
Tue, 05 Jan 2010 22:11:37 +0100
branchstable
changeset 4210 9d9be21640ac
parent 0 b97547f5f1fa
child 11216 efecb78bf929
permissions -rw-r--r--
[forms] fix multiple edit bug introduced by changeset cebdf8ee5ad7 Changeset cebdf8ee5ad7 assumed that edited entity was either explicitly passed to the form or found in first row / first col of the resultset because of the one_line_rset() selector. But one_line_rset() is actually trickier : the selector returns 1 if the resultset has more than one row **if** an explicit row is specified during selection process. This is exactly what is done in the 'muledit' form : for row in xrange(len(self.rset)): form = self.vreg['forms'].select('edition', self.req, rset=self.rset, row=row, #... This changeset thus takes row in consideration to find edited entity if 'row' was explcitly specified.

[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