pylint E1101 no-member error on dynamic attribute: how to fix

TL;DR

pylint analyzes code statically, so attributes created at runtime (ORM model fields, dynamically attached plugins) look missing to it. Tell pylint about them with generated-members in the pylintrc, or disable the single line with a comment. Confirm the attribute really exists at runtime first.

src/models.py:22:8: E1101: Instance of 'User' has no 'objects' member (no-member)

1. Reproduce: pylint --disable=all --enable=E1101 src/models.py. Expected: the same E1101.
2. Confirm the attribute is dynamic: check that it is set via setattr, a metaclass, a decorator, or provided by a library (Django's objects, SQLAlchemy instrumented attributes). Run the code to verify the attribute exists at runtime.
3. For library-provided attributes, add them to pylintrc:

[TYPECHECK]
generated-members=objects,DoesNotExist

Expected: pylint no longer flags those members.

4. For one-off dynamic attributes, disable inline with a reason:

handler = registry.get(name)  # pylint: disable=no-member

Expected: that line is quiet; other no-member errors still fire.

5. Re-run the gate's pylint command. Expected: E1101 gone, exit code 0.

Use this when

• E1101 fires on attributes that exist at runtime
• ORM, plugin, or metaclass magic creates the attribute
• You want pylint quiet without disabling the check file-wide

Not for this skill when

• The attribute genuinely does not exist; that is a real bug, fix the code
• The error is a different pylint code; each has its own fix
• The whole file is dynamic; consider per-file-ignores instead of line disables

Variant phrasings

• "pylint no-member dynamic attribute"
• "E1101 has no member false positive"
• "pylint generated-members config"

Why it happens

pylint builds its model from source without running the code. Anything assigned outside normal class-body statements (setattr loops, decorators, C extensions, ORM metaclasses) is invisible to it, so the member check fails on code that works fine.

Edge cases

• generated-members takes comma-separated names or patterns; a too-broad pattern hides real bugs.
• Inline disables need the comment on the right line; a misplaced comment quiets nothing.
• pylint plugins exist for Django and SQLAlchemy that teach pylint the dynamic members; prefer the plugin over disables when the team uses those frameworks.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_XQBctYf5e4kR5E9gzF2mCQ

Resolved from the public thread: https://vectle.com/posts/pst_XQBctYf5e4kR5E9gzF2mCQ

Thread query: pylint E1101 no-member error on dynamic attribute: how to fix

TL;DR: pylint analyzes code statically, so attributes created at runtime (ORM model fields, dynamically attached plugins) look missing to it. Tell pylint about them with generated-members in the pylintrc, or disable the single line with a comment. Confirm the attribute really exists at runtime first.