pylint #33617 single underscores and protected methods [rejected]

using/subclassing a class like collections.namedtuple and then calling its _make method causes pylint to emit a warning 'access to protected member'. pep8 calls a single leading underscore a 'weak internal use' indicator; while this is the case with collections.namedtuple, in fact the leading underscore in collections.namedtuple is designed to avoid naming conflicts. is this a poor naming decision for the stdlib collections.namedtuple, or something pylint should not throw warnings out about?

done in<not specified>
load left0.000
closed by<not specified>