This is where pylint can definitely help. It won't be able to tell you what is the correct solution, but will be able to tell you the code does nothing. If you wish you can check it again.

1 members found this post helpful.

It told me the code did not do anything, but without any explanation. So, I considered this statement wrong, and proceeded to other things pylint told.

And you learned that was true. And there is a page on the net where all the pylint messages are explained, just you need to look for it.
https://pycodequ.al/docs/pylint-mess...ighlight=w0231

1 members found this post helpful.

The fact that the code does nothing is the explanation. Your conclusion that the message was wrong was... wrong.

Debugging tools do their best to identify problems and bring them to our attention. Usually problems are identified when a parser, or tool, cannot proceed or has a set of symbols it cannot resolve within its current context. The point where that happens can be far from the actual error which causes it, and there may be many possible errors which could produce the same problem, so it is not always possible for the tool to identify the specific cause in any given case.

In this case, it told you that the block of code had no effect - it doesn't do anything - and you are expected to know what you intended for it to do and how it should do so, and to figure out why it does not, in fact, work. It was not possible for it to tell you exactly why it did nothing. If that were the case it could simply fix it for you and continue!

Learn to trust the messages produced by your tools and to understand why any given message was produced. In the occasional case where a message may be superfluous, you should still be able to identify why it was produced!

1 members found this post helpful.

To find what solves errors/warnings is easy. Detailed explanation, I am not sure. Does the link you point explain things like what people did in this thread? (I did not check for the case we are discussing because I am want to know more about possible future uses of that link, compared to other search results I can find)

Yes. I am learning to use this new tool, pylint, as I am learning the basics of Python. Thank you for these comments, astrogeek.

Ok, that is a general page, not for you, not for me, just a general description about what was found. You not only need to understand why it was reported, but you have to know if that was intentional or actually something went wrong.
In this case I can suggest you to post the exact message you got and I will try to explain how should it be handled. (again, in general you need to enter the code - or type - of that message, which is something like W0345 and it will give a special explanation for that, what the authors think about that case).

1 members found this post helpful.

If I knew pylint before starting this thread, I would have understood the other things it pointed in my code. My question would contain only the lines I copied in the post #30, which is the post where I joined everything that solved this thread. So, if more Python help is needed, and information around the web does not help enough, I should write a better question, possibly much smaller and direct.

See you around!