LWN: Comments on "Pylint 1.6.0 released" https://lwn.net/Articles/694424/ This is a special feed containing comments posted to the individual LWN article titled "Pylint 1.6.0 released". en-us Tue, 07 Oct 2025 18:44:39 +0000 Tue, 07 Oct 2025 18:44:39 +0000 https://www.rssboard.org/rss-specification lwn@lwn.net Pylint 1.6.0 released https://lwn.net/Articles/694682/ https://lwn.net/Articles/694682/ jwilk Yes, it is a bit odd; but it's also consistent with how the "in" operator works on dicts. That said, discrepancy between "in" and iterating wouldn't be unprecedented: <pre> &gt;&gt;&gt; s = 'foo'; x = 'oo' &gt;&gt;&gt; x in s True &gt;&gt;&gt; x in iter(s) False </pre> Sat, 16 Jul 2016 19:36:03 +0000 Pylint 1.6.0 released https://lwn.net/Articles/694675/ https://lwn.net/Articles/694675/ mathstuf <div class="FormattedComment"> Having done a bit of Haskell and Rust, iterating over a dictionary to get the pairs is much more useful in my experience. The Python default iteration over a dictionary is odd to me…<br> </div> Sat, 16 Jul 2016 15:28:21 +0000 Pylint 1.6.0 released https://lwn.net/Articles/694674/ https://lwn.net/Articles/694674/ robert_s <div class="FormattedComment"> I'm quite a fan of using .keys() because it's far more "literate" than just iterating through the dict. In fact, most places I see a dict being directly iterated through it is in fact a bug, the author having forgotten to use .items() or .values().<br> </div> Sat, 16 Jul 2016 14:53:49 +0000