Claudiu Popa comments

Results 176 comments of


                                            Claudiu Popa

``duplicate-code`` takes over an hour for a large project even when disabled, if ``reports=yes``

Can you post your `pylintrc` file? Testing with `--disable=duplicate-code` or `--disable=similarities` seems to work as the similarities check does not seem to be enabled any longer.

``duplicate-code`` takes over an hour for a large project even when disabled, if ``reports=yes``

Thanks for the example, but I still cannot reproduce this. Here's what I did: * Modified `SimilarChecker.open()`, `SimilarChecker.process_module()` and `SimilarChecker.close()` to raise an error. `open` is called when preparing a...

``duplicate-code`` takes over an hour for a large project even when disabled, if ``reports=yes``

Wow, that's a stupid bug then. Thank you for the additional details!

Emit new message ``used-global-in-annotation`` instead of ``used-prior-global-declaration``

Thanks, I can reproduce the issue.

aws-api-mcp: Feature Request: Multi-User Support with Per-User AWS Credentials in Python Service

Hi @lhx692135353 Thank you for reaching out. Would support for multiple AWS Profiles help you here? Or where you thinking of a different mechanism?

duplicate-code: referenced code locations are ambigous if from same filename (but different folders)

Hi, thanks for submitting an issue! These improvements make sense.

Linting more than one dir or package, can hide errors or cause wrong errors

Thanks @MarKett for creating the issue. This is the second one recently, we definitely need to fix this behaviour.

no-member false positive related to an import confusion

HI @mitar Thanks for creating an issue. It's true that `pylint` does not consider `__all__` any longer, this is for a couple of years now. The reason we decided against...

no-member false positive related to an import confusion

Gotcha, I see what you mean now. The problem is that somehow `pylint` imports the `foobar` assignment from the file, not the module itself.

no-member false positive related to an import confusion

@mitar pylint stopped considering `__all__` for a couple of years now, but the reason of this bug is somewhat different than handling or not handling `__all__`. Updated the title so...