pylint #57244 two alternating errors for multi-dimensional slicing of numpy arrays [open]

bug submitted on the python-projects ml on August 19 2010 by Klaus Kopec:

I use statements like "a[i, :i] = 0" to slice multi-dimensional numpy arrays. Checking these statements with pylint leaves me with the choice of getting "E203 whitespace before ':'" if I put a space before ':' and "E231 missing whitespace after ','" if I don't put a space there.

Hans Meine update:

That's an interesting case where two sensible rules clash.

IMHO the E231 check should be fixed (or an alternative offered or the like) such that the whitespace is not required within brackets at all.

appeared in<not specified>
done in<not specified>
closed by<not specified>