Solution hints not helpful.

[oseghr]

Completed the solution but kept getting several warnings such below:

Line 12 [C0303 trailing-whitespace] : ["Trailing whitespace"] was reported by Pylint. Which means this code doesn't follow general code style conventions. While this type of issue generally doesn't affect the way code executes, it can hurt readability or the performance of automated tools such as documentation generators or test runners.

Even after following the PEP documentation and expecting the warnings to stop it didn't. Please could this be a bug? The recommendation does not give an example of what the solution might look like.

[github-actions[bot]]

🤖   🤖

Hi! 👋🏽 👋 Welcome to the Exercism Python Repo!

Thank you for opening an issue! 🐍  🌈 ✨

•   If you are requesting support, we will be along shortly to help. (generally within 72 hours, often more quickly).
•   Found a problem with tests, exercises or something else??  🎉
    ◦ We'll take a look as soon as we can & identify what work is needed to fix it. (generally within 72 hours).

​          ◦ If you'd also like to make a PR to fix the issue, please have a quick look at the Pull Requests doc.
             We  💙  PRs that follow our Exercism & Track contributing guidelines!

•   Here because of an obvious (and small set of) spelling, grammar, or punctuation issues with one exercise,
    concept, or Python document?? 🌟 Please feel free to submit a PR, linking to this issue. 🎉

‼️  Please Do Not ‼️ ​        ❗ Run checks on the whole repo & submit a bunch of PRs.               This creates longer review cycles & exhausts reviewers energy & time.               It may also conflict with ongoing changes from other contributors. ​        ❗ Insert only blank lines, make a closing bracket drop to the next line, change a word               to a synonym without obvious reason, or add trailing space that's not an[ EOL][EOL] for the very end of text files.         ❗ Introduce arbitrary changes "just to change things" .         _...These sorts of things are **not** considered helpful, and will likely be closed by reviewers._

• For anything complicated or ambiguous, let's discuss things -- we will likely welcome a PR from you.
• Here to suggest a feature or new exercise?? Hooray! Please keep in mind Chesterton's Fence.
  Thoughtful suggestions will likely result faster & more enthusiastic responses from maintainers.

💛  💙  While you are here... If you decide to help out with other open issues, you have our gratitude 🙌 🙌🏽.
Anything tagged with [help wanted] and without [Claimed] is up for grabs.
Comment on the issue and we will reserve it for you. 🌈 ✨

[BethanyG]

Hi @oseghr,

Thanks for filing this issue. When PyLint complains about "trailing whitespace", it is because there are excess "white space" (non visible but present) characters that are left at the end of lines of code. Things like [tab] (\t) or [space] (' ') or [newline] (\n) or [carriage return] (\r). While these are not fatal, they can cause problems under certain circumstances.

They are particularly annoying because you can't see them, and they (mostly) get ignored ..... until they don't.

Did you paste your code into the online editor? I often do that -- and it creates \n or ' ' at the ends of lines. It's not catastrophic, but if you go through and delete them, the bot will stop complaining. If you have done that already, then it may indeed be a problem with our analyzer -- in which case, we'll look at turning off the analyzer rule.

[BethanyG]

Closing as resolved/abandoned.