[Pythagorean Triplet]: PEP-8 Refactor of Approaches introduction.md File

[Ryrden]

When I faced this code, It was very hard to read, so I've refactored it following Python PEP recommendations

Here is all guidelines I've followed:

• Indentation: "Use 4 spaces per indentation level." PEP 8 - Indentation

• Line Length: "Limit all lines to a maximum of 79 characters." PEP 8 - Line Length

• Blank Lines: "Surround top-level function and class definitions with two blank lines." PEP 8 - Blank Lines

• Spacing Around Operators: "Put a space on both sides of an assignment (=) and comparison (<, >, ==) operators." PEP 8 - Spacing Around Operators

• Comments: "Inline comments should be separated by at least two spaces from the statement." PEP 8 - Comments

[BethanyG]

Hi @Ryrden 👋🏽

Thanks for submitting this. However, this approach was written by someone who was very careful to format the code in a specific fashion. PEP-8 states (emphasis mine):

A Foolish Consistency is the Hobgoblin of Little Minds
...
A style guide is about consistency. Consistency with this style guide is important. Consistency within a project is more important. Consistency within one module or function is the most important.

However, know when to be inconsistent – sometimes style guide recommendations just aren’t applicable. When in doubt, use your best judgment. Look at other examples and decide what looks best.

And while PEP 8 does say line length of 79, we adhere to a line length of 120 to avoid onerous and excessive file length and line breaks. We also make extensive use of implicit concatenation within comprehensions and generator expressions. That is why the code is broken up the way it is.

Finally, there are times where we format code examples to prevent horizontal scrolling on the website. I don't know for sure, but that might be the case here.

I am sorry that this was difficult for you to read, but (for now - we may revisit in the future) we want to keep the file as-is.

[Ryrden]

Never mind, Thanks for the feedback!