(Jul-22-2021, 03:09 PM)alok Wrote: Thanks, "metulburr" on the comment about some books "wizzing thru stuff". They tell you what do do ,but don't say why your doing it.
That is one reason why i liked "Learning Python" book. It would give you numerous examples to do the same thing. In some token this is why some people hate this book. "This is the best way because it is more
pythonic" , this is an alternate way, this is a bad way, this is the old way (python 2.0 at least for my version i read). All doing the same task. Although this is more to read, it gives a better understanding of why your doing something one way versus the other.
In addition, another reason i love this book is there are half paged boxed sections within the book that go further into detail called "why you will care?" that explains why this is helpful and useful for you. There are also mini chapters within each chapter of "Why use X?" that go numerous pages on why use something that is related to the topic of the chapter. These are scattered about the book on everything they talk about. As well as each chapter has a summary, quiz and answers, gotcha warnings, and exercises. So you feel by the end of each chapter that you understand how to code something and why you are coding it the way you are.
The first 75 pages or so dont have any code. It is all just Why do people use python, what are its strengths and weaknesses, why use built-ins, how python runs programs, how you run programs (command line, IDE, clicking files to execute, Shebang line explanation etc.). So this is the introductory of the book, the same applies to the introductory of each chapter.
After reading this book i have read others and find most of them lacking in detail. When i was new i loved how they explained things numerous times with different avenues of reaching the same goal and the explanations to someone whom is totally oblivious. I have answered numerous questions on this forum from solely reading this book alone on making peoples code more pythonic. And it was only because of this book i knew what they were trying to do and how to do it better (pythonic, less code, less chaotic, more understandable, or there is a built in module for that mess your making).