๐ฃ๐๐ฃ-๐ด
-Want to write an "Eye-pleasing" Python code ๐ ๐?
-PEP is a thing you MUST know about while learning or writing a python code
-Python Enhancement Proposal
-Basically a guide to "๐๐ผ๐ ๐๐ผ ๐๐ฟ๐ถ๐๐ฒ ๐ฎ ๐ฏ๐ฒ๐ฎ๐๐๐ถ๐ณ๐๐น ๐ฝ๐๐๐ต๐ผ๐ป ๐ฐ๐ผ๐ฑ๐ฒ?"
BIG Thread ๐งต๐
-Want to write an "Eye-pleasing" Python code ๐ ๐?
-PEP is a thing you MUST know about while learning or writing a python code
-Python Enhancement Proposal
-Basically a guide to "๐๐ผ๐ ๐๐ผ ๐๐ฟ๐ถ๐๐ฒ ๐ฎ ๐ฏ๐ฒ๐ฎ๐๐๐ถ๐ณ๐๐น ๐ฝ๐๐๐ต๐ผ๐ป ๐ฐ๐ผ๐ฑ๐ฒ?"
BIG Thread ๐งต๐
We all know that besides having logic and coding in any programming language, there is an important factor that is "coding style"
-How we are writing comments?
-How we are giving spaces?
-How to import libraries?
-etc
These things are very important to write a beautiful code!
-How we are writing comments?
-How we are giving spaces?
-How to import libraries?
-etc
These things are very important to write a beautiful code!
For Python, PEP 8 has emerged as the style guide that most projects adhere to.
It promotes a very readable and "eye-pleasing" coding style. ๐
A code which anyone will love to read and is very easily understandable.
It promotes a very readable and "eye-pleasing" coding style. ๐
A code which anyone will love to read and is very easily understandable.
Further in this thread ๐งต
I am going to explain some important points of PEP-8, which are important to write a beautiful code in Python๐
I am going to explain some important points of PEP-8, which are important to write a beautiful code in Python๐
๐ ๐ฎ๐
๐ถ๐บ๐๐บ ๐๐ถ๐ป๐ฒ ๐๐ฒ๐ป๐ด๐๐ต ๐ข
Limit all lines to a maximum of 79 characters.
For docstrings or comments, the line length should be limited to 72 characters.
In long with statements, "/" are acceptable otherwise break it and continue in the next line.
๐Example
Limit all lines to a maximum of 79 characters.
For docstrings or comments, the line length should be limited to 72 characters.
In long with statements, "/" are acceptable otherwise break it and continue in the next line.
๐Example
๐๐ป๐ฑ๐ฒ๐ป๐๐ฎ๐๐ถ๐ผ๐ป๐
-Use 4 spaces for indentation
-Add 4 spaces (extra level of indentation) to distinguish arguments from the rest
-Spaces are the preferred indentation method
-Tabs should be used solely to remain consistent with code that is already indented with tabs!
-Use 4 spaces for indentation
-Add 4 spaces (extra level of indentation) to distinguish arguments from the rest
-Spaces are the preferred indentation method
-Tabs should be used solely to remain consistent with code that is already indented with tabs!
๐๐ผ๐บ๐บ๐ฒ๐ป๐๐๐ฏ๏ธ
- Comments that contradict code are worse than no comments
- Never use comments in a place where it is not needed
-Comments are indented to the same level as that code.
-Each line of a block comment starts with a # and a single space
- Comments that contradict code are worse than no comments
- Never use comments in a place where it is not needed
-Comments are indented to the same level as that code.
-Each line of a block comment starts with a # and a single space
๐๐ผ๐ฐ๐๐บ๐ฒ๐ป๐๐ฎ๐๐ถ๐ผ๐ป ๐ฆ๐๐ฟ๐ถ๐ป๐ด๐ ๐
-Conventions for writing good documentation strings (a.k.a. "docstrings") are immortalized in PEP 257.
-Write docstrings for all public modules, functions, classes, and methods.
-Docstrings are not necessary for non-public methods
-Conventions for writing good documentation strings (a.k.a. "docstrings") are immortalized in PEP 257.
-Write docstrings for all public modules, functions, classes, and methods.
-Docstrings are not necessary for non-public methods
๐๐น๐ฎ๐ป๐ธ ๐๐ถ๐ป๐ฒ๐ ๐ณ
-Surround top-level function and class definitions with two blank lines.
-Method definitions inside a class are surrounded by a single blank line.
-Use blank lines in functions, sparingly, to indicate logical sections.
-Surround top-level function and class definitions with two blank lines.
-Method definitions inside a class are surrounded by a single blank line.
-Use blank lines in functions, sparingly, to indicate logical sections.
๐๐บ๐ฝ๐ผ๐ฟ๐๐ โ
-Should be on different lines
-Should be on the top
-Grouped in the following order
-Standard library imports
-Related third-party imports
-Local application/library specific imports
-You should put a blank line between each group of imports
-Should be on different lines
-Should be on the top
-Grouped in the following order
-Standard library imports
-Related third-party imports
-Local application/library specific imports
-You should put a blank line between each group of imports
This whole thread is NOT the complete PEP-8 style guide, but these are the most important points from it!!
You can write an eye-pleasing python code that everyone wants to read If they see the code!
You can access the complete PEP-8 guide here ๐
๐ python.org/dev/peps/pep-0โฆ
You can write an eye-pleasing python code that everyone wants to read If they see the code!
You can access the complete PEP-8 guide here ๐
๐ python.org/dev/peps/pep-0โฆ
Hey,
Thanks for coming to the end of the thread โค๏ธ
I hope, you understand what PEP is and how to write a beautiful python code :)
If you like this thread, Retweet the first tweet of the thread.
So that we all can learn about it!!
Thanks for coming to the end of the thread โค๏ธ
I hope, you understand what PEP is and how to write a beautiful python code :)
If you like this thread, Retweet the first tweet of the thread.
So that we all can learn about it!!
https://twitter.com/Sauain/status/1417375145769914368?s=20
โข โข โข
Missing some Tweet in this thread? You can try to
force a refresh
ใ
