[code-quality] used-before-assignment warning with :=

I was running pylint (2.6.0) in VS Code against a module, the code was working. if (amt := self._data[index.row()][index.column()]) \ and float(amt) < 0.0: return QColor('red') I got the above error and had to change it to the be

[code-quality] Re: used-before-assignment warning with :=

What was the exact error you encountered? Sent from my phone with my typo-happy thumbs. Please excuse my brevity On Mon, May 31, 2021, 09:19 Ed Lipson wrote: > I was running pylint (2.6.0) in VS Code against a module, the code was > working. > > if (amt := self._data[index.r

[code-quality] Re: used-before-assignment warning with :=

Hello, You should upgrade pylint to the latest version, in order to get supports for the walrus operator (2.8 or superior has it, maybe even 2.7.4). The match pattern will only be supported in the next major version too (2.9.0). Best regards, Le lun. 31 mai 2021 à 16:22, Ian Stapleton Cordasco <

[code-quality] Prospector maintenance

Hello, I don't see any committer that is active on the Prospector project, I'm I right? If yes, is there any plan to maintain this project? Sincerely, Stéphane -- *Stéphane Brunner* Geospatial Solutions Software Developer *camptocamp* INNOVATIVE SOLUTIONS BY OPEN SOURCE EXPERTS camptocamp.co

[code-quality] Re: used-before-assignment warning with :=

This was an issue with pylint and was fixed in pylint v 2.8.0. Changelog: http://pylint.pycqa.org/en/latest/whatsnew/changelog.html#what-s-new-in-pylint-2-8-0 On Mon., May 31, 2021, 7:19 a.m. Ed Lipson, wrote: > I was running pylint (2.6.0) in VS Code against a module, the code was > working. >

[code-quality] Pyside2, QAbstractItemModel subclassed setData and changedData.emit()

I'm writing pyside2 code, using the QAbstractItemModel class. I've subclassed setData. The pyside2 doc says to explicitly emit the changedData signal if this is done. QAbstractItemModel — Qt for Python pylint does

[code-quality] Re: Prospector maintenance

I would also like to know this! It doesn't seem like there is currently anyone active who is responsible for maintaining/releasing the code. There's at least one active PRs that should be merged (providing a critical update from pylint 2.5), and there hasn't been a release since October of last

[code-quality] Re: Prospector maintenance

Hi all, especially Stéphane and David, I'm the original creator of the prospector tool so it's my fault that it has become unmaintained. I did find a maintainer a while ago who did a fantastic job keeping it going but I assume they're now no longer able to and I had kind of fallen out of love with

[code-quality] Re: Prospector maintenance

Hey there folks, yes there is and I've been struggling to come back maintaining the project. There some personal events at the moment that are consuming the time I'd have to be contributing to prospector. We are surely seeking more active contributors to help keep things running. I'm yet to review