“Hammurabi, Hammurabi, I beg to report to you,
\nIn Year 1, 0 people have starved.
\n101 people came to the city
\nThe population is now 124
\nWe harvested 4.5 bushels per acre
\nWe planted 998 acres of wheat
\nBut rats at 300 bushels of wheat
\nYou now have a surplus of 1443 bushels of wheat<\/p>\n
How many acres do yo uwish to feed to the people?
\nHow many acres do you wish to plant with seed?<\/p>\n
Oh, and you have died of Cholera!”<\/p><\/blockquote>\n
Or, this one:<\/p>\n
I went to a special high school, in an era when individuals and high schools alike did not have computers, but we did. Since we were a University normal school, we had account and terminal room access to the UNIVAC 1108 computer at the University (see photo above). There were no computer games in those days, so you had to write your own, and store them on tape. Paper tape, not magnetic tape (the magnetic tape was reserved for use by actual University students and faculty, for the most part).<\/p>\n So we wrote and fiddled with programs in BASIC, the intro language of the day. BASIC was a great language, but is widely regarded today as a horrible language. Truth is, it was easy to program in, had reliable interpreters, and eventually, advanced versions became fully OOPish and lost silly things like line numbers.<\/p>\n Today’s equivilant of BASIC, for the simple reason that it is one of the programming languages people often start on, but similar for other reasons as well, is Python.<\/p>\n Python was invented by Benevolent Dictator For Life Guido van Rossum. Guido was a big fan of Monty Python back in 1989 when he invented an interpreter to run a script language that didn’t exist yet but was knocking around in his head. A script, in computer world, is a series of commands in a file that can be run like it was a computer program, but where the code is not turned into an executable file to run independently, but rather, run by an “interpreter” which carries out the commands ad hoc each time the script is called. That is how BASIC originally ran, and that is how Python works.<\/p>\n Et magis est, ut in fabula.<\/p>\n Python has evolved over the years to become one of a small number of languages that can do pretty much anything. The language itself is fairly simply yet powerful and flexible. In writing Python programs (the language is too fancy to use the term “script” comfortably, though that is technically what the programs are) one has access to a large number of libraries of pre-existing code. These libraries are extensive, intensive, flexible, and powerful. The programs run very efficiently.<\/p>\n What software that you know about is written in Python? Well, DrobBox is written in Python, which is not surprising, since Benevelont Dictator van Rossum works for Dropbox (or did anyway, not sure if he is still there). Google uses Python for pretty much everything, so when you “google” something, you are using the Linux operating system running a Python script accessing data created and maintained by Python scrips. Also, Python was underwent much of its development with support from Google.<\/p>\n Many of the GNU Linux utilities and software in use today that is not from the original cadre of mainly C-xx (a different family of languages) applications are written in Python. So, again, the basic computer services we rely on, such as Google, ultimately use Python in many different ways.<\/p>\n And, Python has become one of very few widely used scientific software tools. If you are going to grow up and become a scientist, you will want Python skills.<\/p>\n And this is where we come to the new 4th edition, Invent Your Own Computer Games with Python<\/a> This is an excellent way to learn Python, if you are a kid or not. Little kids can learn with their adult guide, and older kids will eat this book up in an afternoon or two.<\/p>\n The Table of Contents will give you an idea of what it covers:<\/p>\n First, on how to set up and use Python:<\/p>\n Chapter 1: The Interactive Shell Then some very simple games:<\/p>\n Chapter 3: Guess the Number Then how to use a key feature to help you more easily write complex programs: Then a pretty complex program (but still very doable):<\/p>\n Chapter 7: Designing Hangman with Flowcharts Then many more programs of various levels of difficulty:<\/p>\n Chapter 10: Tic-Tac-Toe Then some advanced programming and tools, and more games:<\/p>\n Chapter 17: Using Pygame and Graphics Many of the programs are designed to run on the command line, but still use cool (in a retro sort of way) graphics, but the book gets you started on using modern day window-deployed graphics.<\/p>\n Al Sweigart is a software developer who teaches programming to kids and adults. He is the author of Automate the Boring Stuff with Python: Practical Programming for Total Beginners<\/a> Go to the No Starch Press web site to access the code and other resources, and to find a list of errors and updates. In a regular book about something, say, Abraham Lincoln, a typo is not a big deal. In a computer programming book, a typo can be a big deal.<\/p>\n For example, reading “In 1860, Lincoln secured the Republican Party presidential nomination as a moderate from a wing state,” instead of a “S<\/strong>wing state” is not going to cause a disaster. But in 1962, the Mariner spacecraft had to be destroyed moments after takeoff because a “-” was written instead of a “–<\/sup>“.<\/p>\n Anyway, great book. Enjoy it!<\/p>\n","protected":false},"excerpt":{"rendered":" Ah yes, I remember it well. “Hammurabi, Hammurabi, I beg to report to you, In Year 1, 0 people have starved. 101 people came to the city The population is now 124 We harvested 4.5 bushels per acre We planted 998 acres of wheat But rats at 300 bushels of wheat You now have a … Continue reading Write Computer Games In Python<\/span> ![\"screen-shot-2017-01-14-at-3-04-24-pm\"](\"https:\/\/i0.wp.com\/scienceblogs.com\/gregladen\/files\/2017\/01\/Screen-Shot-2017-01-14-at-3.04.24-PM-1.png\")
<\/a>
\nRemember?<\/p>\n
\nChapter 2: Writing Programs<\/em><\/p>\n
\nChapter 4: Jokes
\nChapter 5: Dragon Realm<\/em><\/p>\n
\n
\nChapter 6: Using the Debugger<\/em><\/p>\n
\nChapter 8: Writing the Hangman Code
\nChapter 9: Extending Hangman<\/em><\/p>\n
\nChapter 11: Bagels
\nChapter 12: Cartesian Coordinates
\nChapter 13: Sonar Treasure Hunt
\nChapter 14: Caesar Cipher
\nChapter 15: Reversi
\nChapter 16: AI Simulation<\/em><\/p>\n
\nChapter 18: Animating Graphics
\nChapter 19: Collision Detection and Input
\nChapter 20: Sounds and Images
\nChapter 21: Dodger<\/em><\/p>\n