docs/wtfpython
docs/wtfpython
1
0
Fork 0
mirror of https://github.com/satwikkansal/wtfpython synced 2024-11-22 02:54:25 +01:00
Code Releases Activity

Slightly update the description

Browse Source
This commit is contained in:
Satwik Kansal 2018-01-19 19:03:37 +05:30
parent 10cd5e06a2
commit 7d667bb3fd
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
README.md vendored
View File

@ -4,7 +4,7 @@
[![WTFPL 2.0][license-image]][license-url] [![WTFPL 2.0][license-image]][license-url]
Python, being awesome by design high-level and interpreter-based programming language, provides us with many features for the programmer's comfort. But sometimes, the outcomes of a Python snippet may not seem obvious to a regular user at first sight. Python, being a beautifully designed high-level and interpreter-based programming language, provides us with many features for the programmer's comfort. But sometimes, the outcomes of a Python snippet may not seem obvious to a regular user at first sight.
Here is a fun project attempting to collect such classic and tricky examples of unexpected behaviors in Python and discuss what exactly is happening under the hood! Here is a fun project attempting to collect such classic and tricky examples of unexpected behaviors in Python and discuss what exactly is happening under the hood!
@ -156,10 +156,10 @@ All the examples are structured like below:
A good way to get the most out of these examples, in my opinion, will be just to read the examples chronologically, and for every example: A good way to get the most out of these examples, in my opinion, will be just to read the examples chronologically, and for every example:
- Carefully read the initial code for setting up the example. If you're an experienced Python programmer, most of the times you will successfully anticipate what's gonna happen next. - Carefully read the initial code for setting up the example. If you're an experienced Python programmer, most of the times you will successfully anticipate what's gonna happen next.
- Read the output snippets and - Read the output snippets and,
+ Check if the outputs are the same as you'd expect. + Check if the outputs are the same as you'd expect.
+ Make sure know the exact reason behind the output being the way it is. + Make sure know the exact reason behind the output being the way it is.
- If no, read the explanation (and if you still don't understand, shout out! and create an issue [here](https://github.com/satwikkansal/wtfPython)). - If no, take a deep breath, and read the explanation (and if you still don't understand, shout out! and create an issue [here](https://github.com/satwikkansal/wtfPython)).
- If yes, give a gentle pat on your back, and you may skip to the next example. - If yes, give a gentle pat on your back, and you may skip to the next example.
PS: You can also read these examples at the command line. First install the npm package `wtfpython`, PS: You can also read these examples at the command line. First install the npm package `wtfpython`,