pylint #92253 Warn of mistaken trailing commas creating tuples. [open]

Often I mistakenly have an assignment statement with a trailing comma. For example:
    x = 1,          # I intended: x = 1
That syntax is acceptable in python, so no errors are reported. But it's not what I intended and it can create bugs that are difficult to pin down. I find this syntax to be unfortunate. The comma is hard to see on a code scan so it leads to bugs. Besides, python has a perfecty good alternative syntax.
    x = (1,)
Would it be possible for pylint to warn me of instances of the first syntax do I can fix it.
done in<not specified>
closed by<not specified>