News for hackers. Stuff that matters.

A comment on 5% of 666 Python repos had comma typo bugs (inc V8, TensorFlow and PyTorch). Parent comment

Re:5% of 666 Python repos had comma typo bugs (inc V8, Tenso... by mikepurvis on Friday January 07, 2022 @12:57PM (#29842313)
I would have thought it would be a no-brainer to just ban it and insist on an explicit + operator. I'm pretty surprised that issue was so flippantly closed.
[ Parent | on HN ]
Re:5% of 666 Python repos had comma typo bugs (inc V8, Tenso... by thaumasiotes on Friday January 07, 2022 @01:03PM (#29842404)
> I would have thought it would be a no-brainer to just ban it and insist on an explicit + operator.

Maybe as a matter of linting. As a matter of language design, I think + for string concatenation is a big mistake; using different symbols for numeric addition and string concatenation is something Perl got right.

[ Parent | on HN ]
Re:5% of 666 Python repos had comma typo bugs (inc V8, Tenso... by mikepurvis on Friday January 07, 2022 @01:12PM (#29842550)
Yes, I meant as a matter of linting. I can understand the arguments being different for the language as a whole, particularly when legacy compatibility is a consideration.

But my impression using pylint is that its default settings are wildly opinionated, hence the surprise that this wouldn't have fallen under that umbrella.

[ Parent | on HN ]
Re:5% of 666 Python repos had comma typo bugs (inc V8, Tenso... by ReleaseCandidat on Friday January 07, 2022 @01:06PM (#29842454)
The PR has been merged (for lists and tuples and sets only).

https://github.com/PyCQA/pylint/pull/1655

[ Parent | on HN ]