Aug-29-2017, 01:03 PM
(This post was last modified: Aug-29-2017, 01:16 PM by defenderofthebit.)
i see your point, and i understand the lack of fandom, most especially for an outdated version of the book. i have been hunting many tutorials and i will look into your links, what i am asking for is not the same as the python documentation, because as stated above, the documentation on the python website, while it does explain each individual part in detail, it incredibly lacks on the usage of them together in a comprehensible way, and lacks example, think of it less as work to re write what is written, and more of a fun project to write new code and label it in terms more understandable, also im not asking to repeat the textbook to me... im asking to explain the usage of what the documentation explains through showing the example and explaining as it goes, i somewhat expect functional code with explanations embedded. the documentation explains individual parts but lacks cohesion, the tutorials explain cohesion but without defining individual part, and even if they do, they only give single, or limited uses of these statements, which i have seen to be much more versitile, but with no explanation of how that versatility works. im not asking you to parrot things. im asking everyone to help me explain as we go, instead of just explaining, or just going, like 995 of the tutorials and documentations tend to do. so far out of literally over 30 tutorials and different resources of documentation, i have found ONE that comes close to what i am looking for. it is at http://anh.cs.luc.edu/handsonPythonTutorial/idle.html lines 0-39. but even that feels somewhat lacking and could be better explained as embedded comments like my example above shows.
also i want to say that group discussion and group efforts towards creating this type of "master code" (if you will) could help more than just me, find new ways and methods of understanding and applying code. it is not only for me, do i make this request. and i do want to volunteer to be an active participant in this. i will carry a shovel and dig the dirt. please do not put me in a high chair for a spoon feeding. it is not my intent. i apologize if i seem rude, i do not intend to be a waste of time.
i demand a shrubber!
maybe i am a poor salesman, but i believe in my product. if anything it will help your website compile its own documentation, open source, which would be more human comprehensible than any other in existence. like a group writing a thesaurus for a dictionary which contains no grammar. and a good source of public snippets, complete with embedded explanations. revolutionary. now may i ask what more question?
WHAT IS YOUR FAVORITE COLOR?!
also i want to say that group discussion and group efforts towards creating this type of "master code" (if you will) could help more than just me, find new ways and methods of understanding and applying code. it is not only for me, do i make this request. and i do want to volunteer to be an active participant in this. i will carry a shovel and dig the dirt. please do not put me in a high chair for a spoon feeding. it is not my intent. i apologize if i seem rude, i do not intend to be a waste of time.
i demand a shrubber!
maybe i am a poor salesman, but i believe in my product. if anything it will help your website compile its own documentation, open source, which would be more human comprehensible than any other in existence. like a group writing a thesaurus for a dictionary which contains no grammar. and a good source of public snippets, complete with embedded explanations. revolutionary. now may i ask what more question?
WHAT IS YOUR FAVORITE COLOR?!