2nd Edition of Learn Python the Hard Way Released
theodp writes "Are you or your kid intrigued by Python, but not quite ready to purchase an in-depth O'Reilly book? Zed A. Shaw's 2nd edition of Learn Python The Hard Way may be a friendlier option. Shaw's path to Python programming is simple: 1. Go through each exercise, 2. Type in each sample exactly, 3. Make it run. If $60 for the hardcover is too much to ask, or $15.99 for paperback, you can spend a measly buck for the PDF/ePub download. Still too steep? OK, there's even a free online HTML edition. After completing the 52 exercises, Shaw's concluding Advice From An Old Programmer says, 'Which programming language you learn and use doesn't matter. Do not get sucked into the religion surrounding programming languages as that will only blind you to their true purpose of being your tool for doing interesting things.'"
How is that the hard way? What ever happened to sharpening your teeth on man pages and samples written by people far better than you?
I expect the language laid out in monospaced ASN.1 tables from the get-go.
They can be in your way, they can make you jump though hoops, they can require you to create so much noise that you need tools to write anything in it (java is a prime example). If you are a truly good programmer, you want a language that does not tell you how to do things and just lets you do what you think is right. Even if that language has less extensive libraries than others.
Personally, I like Python, Lua and C at this time. Python does OO but does not force a specific, limited model on you as most other OO languages do. The one thing that comes close is Eiffel, but at the price of the compiler needing global scope. Lua is just plain elegant minimalistic and again supports OO, but as you see fit, not some restrictive inheritance model. And C just lets you do what you want, very fast if you know what you are doing, although OO, while feasible, has no language support at all. But often you can do without in C anyways. (Yes, even people that understand and like OO sometimes find that not using it is better.) In addition, all three languages are light-weight.
As to C++, I think that abomination would have been better aborted before birth. You need to know far too much about its internal execution model to write efficient code. At the same time, it is not light-weight anymore.
I also have observed that most of the Java crowd never manages to get to the level of being even mediocre programmers. To me these people look more like "library call sequencers" that could not ever do anything useful without these libraries and development tools that automatize a lot. Quite often this leads to slow, complex and insecure solutions, where the code is basically unreadable due to too much code, to many layers, too much abstractions and no insight on the part of the programmer. Sometimes Java code is 95% clutter and noise. This problem is less pronounced with other languages. One piece of advice I therefore give to anybody that wants to learn programming is to avoid Java like the plague. This is definitely only a language for quite advanced programmers, although the typical Java programmer is very far from that indeed.
Most ACs are not even worth the keystrokes to insult them. Be generically insulted by this and ignored otherwise.
"A programmer will eventually tell you to use Mac OSX or Linux. If the programmer likes fonts and typography, they'll tell you to get a Mac OSX computer. If they like control and have a huge beard, they'll tell you to install Linux. Again, use whatever computer you have right now that works."
Philip Greenspun has some good titles: Philip and Alex's Guide to Web Publishing (dated, but I paid cash money for it back in the day), Software Engineering for Internet Applications, and SQL for Web Nerds. If you find yourself in the DB2 world, Graeme Birchall's DB2 SQL Cookbook is a must-have.
I have a fever, and the only cure is more COBOL.
Looks like a good attempt on programming, but if I am starting on Python today, I'd prefer using the current version.
This is a good price-point; yet, if you want to do anything more than an evening with Python, try...
http://diveintopython3.org/ or
Computer Programming for Kids http://cp4k.blogspot.com/
I am a novice level programmer in C++/Python and I thought I could benefit from this book. But the exercises seem to be ridiculously simple and it seems a book only suited for someone with zero or negligible programming background.
A month or so ago I decided to pick up a Python book at the Borders-is-dying sale, and while it's from O'Reilly, the book is too much of a reference - a lot of bottom-up "here's are six different list-like things" and "nobody expected the Spanish Inquisition, which is why you need to use this method to catch the exception it throws, but you can change that by overloading _ _ that _ _ method name's variable __pope__ or using _ComFyChaiR_ instead, but you can't set __pope__ to French, because that object uses __antipope__ instead, though in later versions you can modify it by using Cardinal()."
A friend of mine pointed me to python.org's tutorials", which were going to be my next step, but this looks pretty simple and accessible too.
Bill Stewart
New Fast-Compression-only CPR http://preview.tinyurl.com/dy575ks
Too late! At $1 (£ 0.65) and ease of paypal, I literally just grabbed myself a PDF copy. In my defence, the popular 3D program Blender uses Python.
Check out MIT's OCW. Free lectures with a GPL Python programming book that does an excellent job at explaining programming and the Python language. The lectures are bad quality but the projects are good for practice.
Oh, you think watching Python on VHS is the hard way, do you? Why, in my day, if we wanted to see a good Monty Python skit we had to go kidnap the performers, construct a set, and buy enough booze to get them drunk enough to perform. VHS? Luxury.
When you bought the PDF, what format was it - Kindle-shaped, or letter-sized paper (A4 or 8.5x11 etc.) or something else? If it's Kindle, it looks like a good price.
Also, I was surprised by the terms of the free HTML - you're not allowed to change it! The big reason for reading it in that format is precisely to change it, by copying code examples and pasting them into your Python interpreter to see what they do :-)
Bill Stewart
New Fast-Compression-only CPR http://preview.tinyurl.com/dy575ks
One of the things I really liked about C was that once you've learned a few basics like how pointers and structs work, looking at code written by people much better at C than you just makes sense and comments like /* you are not expected to understand this */ are quite rare. That wasn't as true about C++ or Java, where many kinds of things are readable (after getting the basic "object" stuff down") but some of the template stuff is too obscure. It wasn't true at all about APL or PERL :-)
I was expecting Python to resemble LISP with a different syntax, but it's looking a lot messier than even Common LISP, and of course a lot of the moving parts are hidden in the large number of pre-written modules that come with Python.
Bill Stewart
New Fast-Compression-only CPR http://preview.tinyurl.com/dy575ks
I'd heard of "Learn Python the Hard Way", but I thought it was a joke.
If you know any other programming language, Python is very easy.
You can always grab the ePub for that same $1 and use Calibre to convert it to a format the Kindle can use. I just bought it myself, looks great on my Nook.
Today is red jello day - all workers must eat all of their red jello. Failure to comply will result in five demerits.
and then from the next paragraph:
Learn Python "the Hard Way" to me implies an advanced book. It seems they meant "Learn Basic Python Well". I kind of prefer this title, too--it's much friendlier for the apparent target audience, even if it's not as catchy.
Pro Git is a great resource if you want to get into Git. (You can buy a dead tree version as well.)
There's no -1 for "I don't get it."
By watching The Life of Brian, Monty Python's Flying Circus, and Monty Python and the Holy Grail
General Relativity: Space-time tells matter where to go; Matter tells space-time what shape to be.
Actually you're not supposed to copy and paste the code. That would definitely not be the hard way. You are supposed to retype the examples yourself, just like back when books were print only.
It is the libraries, frameworks, and targets. These are the difference between just learning a language and having grown up with it.
No, the fact the language doesn't deal with the real programmer's life issues with (eventually) bad text editor, or simply because there will always people with bad or diverging habits is python downside.
In the same way that the the it is difficult to drive nails into wood with a nail file is the downside of a nail. Once you apply the correct tool in the correct fashion the problem vanishes.
Really all you have to do is alias python to path/python -tt and there is no problem only a syntax error. Or Alternatively, I have a "bad habit" I tend on occasion to leave the semi-colon off the end of the line when writing in Perl or C. Thus both Perl and C's "downside" is that they "[don't] with the real programmer's life issues .. simply because there will always people with bad or diverging habits." Makes sense to me.
The fact that one may or may not use a text editor that you consider "good"
I wrote "... whatever text editor you have you ought to be able to set this up." If you can't then the editor is not "good," but not as a function of my personal aesthetics, but due to its lack of fitness to do its job. Are there really programmer's text editors out there that cannot substitute a tab for four spaces throughout a file?!!
You may "like it", and I can see why ... but do not dismiss the issues associated with it.
After 2 or 3 months annoyance with the tabs/spaces "issue" followed by about 10 years withoIn factut even noticing any, I think I'm entitled to dismiss the "issues associated with it."
As it happens I wasn't dismissing the issue, I was offering advice about how anyone still suffering from this issue could dismiss it.
Better to be despised for too anxious apprehensions, than ruined by too confident a security. --Edmund Burke
Most of this "advice" is bullshit. The "line I've been programming for a very long time. So long that it's incredibly boring to me. At the time that I wrote this book, I knew about 20 programming languages and could learn new ones in about a day to a week depending on how weird they were. " gives it away.
Sure if you've got a background covering C you can pick up those languages based on C syntax pretty quickly - in terms of writing raw statements - but that means very little as most of the heavy lifting these days is done using the supporting libraries. Sure myself I picked up C# syntax in about that, but groking .Net to a productive level takes a fair bit longer. Even Javascript, which appears very simple for someone with a C background is deceptively simple to think you've got but you're probably missing out on the subtleties whole protoypical inheritance model. And then there's C++. Can anyone who doesn't code C++ as their day-job for less than two years really claim to have C++ and completely under their fingers?
And we haven't even considered more unusual things like Haskell or Prolog, or even Lisp where it's not just a question of the syntax. Sure if by 'picking up' you mean getting to the point of being able to code Quicksort then yes, but otherwise - well I call bullshit. And I've got over 20 years experience and an average of one language a year over that (but I'd only claim to really have half a dozen completely understood).
This is exactly how I like to learn, a dew lines about the code, the code, and expected output. Its concise, no crud in there. Its a format i'd like to see more of. I remember reading a C++ book, one of those monster ones from the late 90s that used up about 50 pages printing out encoded resource files, pages and pages of non-human readable crap. (Being a nub at the time I actually typed a lot of it out)
> 1. Go through each exercise, 2. Type in each sample exactly
> Do not get sucked into the religion surrounding programming
> languages as that will only blind you to their true purpose of being
> your tool for doing interesting things.
Yes, but to type in the programming exercises, do you recommend using vi or emacs? :-/
Agree. I'm always being told how wonderful/portable it is but every time I try to run a Python program I get "wrong version" or something.
Chapter 0 of the book has "Make sure you install Python 2 not Python 3.". Uhuh, there's a language I want to invest some time in. Not.
Is there a reason why the language designers didn't put some kind of versioning into their language when they took the decision that backwards compatibility wasn't important to them? Some sort of shebang on the first line with the version number...? It's not difficult.
The other setup advice, ie.:
Open Edit->Preferences select the Editor tab.
Change Tab width: to 4.
Select (make sure a check mark is in) Insert spaces instead of tabs.
Turn on "Automatic indentation" as well.
Doesn't inspire me to learn Python either. Why impose a rigid spacing structure on a language in a world where tabs aren't standardized (and never will be)? Brackets (or whatever) aren't difficult.
I grok that Python is great for I'm-too-busy-to-learn-a-proper-language programmers to knock batch scripts together quickly but it's not a language for serious work (ie. programs that take more than a day or so to write).
No sig today...
So, your post comes down to "I've never used python, let alone programmed in it, but I know enough to insult those who do".
I programmed in mostly C++ and java (with some lisp and ML) for 20 years before I tried python, and when python is a little sluggish for my needs, I fall back on them but I hardly ever need to. Maybe you're the one who can't be bothered to learn something new and are looking to justify that to yourself.
http://rareformnewmedia.com/
Yes, but to type in the programming exercises, do you recommend using vi or emacs? :-/
The author suggests gedit, for all platforms, which is a fair enough suggestion. However he then insists on using spaces over tabs, without any explanation of the relative merits, thus already choosing a side in yet another programming disagreement. A simple "choose one and stick to it" would have sufficed.
Personally If I follow the book I'll be using vim + tabs, because those are what I'm used to and prefer, but that's just me.
Cited from http://learnpythonthehardway.org/book/ex50.html :
"Other Python programmers will warn you that lpthw.web is just a fork of another web framework called web.py, and that web.py has too much "magic". If they say this, point out to them that Google App Engine originally used web.py and not a single Python programmer complained that it had too much magic, because they all worked at Google. If it's good enough for Google, then it's good enough for you to get started. Then, just get back to learning to code and ignore their goal of indoctrination over education."
Hmmm... I remember times when Guido v.Rossum, Tim Peters and others were working at a company called BeOpen.com ... may this shows my age.
Peter Funk, Oldenburger Str.86, D-27777 Ganderkesee, Germany
Neither:
If a programmer tells you to use vim or emacs, tell them, "No." These editors are for when you are a better programmer. All you need right now is an editor that lets you put text into a file. We will use gedit because it is simple and the same on all computers.
The road to tyranny has always been paved with claims of necessity.
Adobe Reader X "Properties" says it's been made using LaTex and is 8.25 by 10.75 inches (20.1x 27.3 cm), doesn't look very A4 to me.
Yes, but to type in the programming exercises, do you recommend using vi or emacs? :-/
The author suggests gedit, for all platforms, which is a fair enough suggestion. However he then insists on using spaces over tabs, without any explanation of the relative merits, thus already choosing a side in yet another programming disagreement. A simple "choose one and stick to it" would have sufficed.
Personally If I follow the book I'll be using vim + tabs, because those are what I'm used to and prefer, but that's just me.
I think that's a foolish decision.
Sure, either tabs or spaces will work fine, as long as you're consistent. The problem is that once you move beyond toy programs you will be sharing code with other developers, modifying code you get from other sources, etc. And that other code will use spaces, which means that when you mix your tab-using code with it, stuff will break.
When writing Python, follow the Python community's coding conventions, and one of the strongest and most important is to use spaces, not tabs, for indentation.
Note to ACs: I usually delete AC replies without reading them. If you want to talk to me, log in.
Does OSX actually have any advantages over any other OS when it comes to typography?
"You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
Sorry, had to say it...
Can't beat that.
You don't have to hit enter when you reach the end of the textbox. There is a thing called word wrap.
Programming Perl is pretty awesome.
nihilism where the most meaningful syntactic element is the empty nothingness of space.
Is there a reason why the language designers didn't put some kind of versioning into their language [...] Some sort of shebang on the first line with the version number...? It's not difficult.
C:\>python
>>> import sys
>>> sys.version
'2.6.5 (r265:79096, Mar 19 2010, 21:48:26) [MSC v.1500 32 bit (Intel)]'
>>> sys.version_info
(2, 6, 5, 'final', 0)
You were saying?
I perused the chapters from start to end, skimming over all-too familiar ones, and looking at the writing and examples explained. It's a fine read for people new to programming.
It may not be very technically in-depth, may not cover all examples, and it may not warn about all the caveats, but it's a good place nonetheless.
That's the point of this book.
If you already know programming, you might find it a bit slow, and would probably prefer something like Dive Into Python.
I like the creative examples near the end, which introduces ideas like string manipulation and sentence parsing.
I found some of the writing too prolix, for my liking, but that's just me. And no, I don't have ADHD; my other personality might though.
Kudos to the Author, Zed.
It's your loss. I spent a lot of time learning "proper languages" before getting around to trying Python.
When I finally got around to looking at the language, I regretted not learning it sooner. I was able to both learn the language and write the program that I needed in less time than it would have taken me using the languages I already knew.
Python is a handy tool to have available. Sure, it isn't the best tool for every job, but neither is duct tape.
I never copy paste code even when I can and probably should. Instead I type it out. I find my understanding of what it does deepens, and I tend to retain it longer.
I am Bennett Haselton! I am Bennett Haselton!
Python is a language that takes a day to relearn every time you have to switch to it. I foolishly chose it over Java for my Google app engine code. Only a few hundred lines, but so stupidly different in syntax to every other language that I regularly use it's just a pain. I hate it. Python is fine if that's the only language you use, or if you have a keyboard where it's really hard to type { and }.
I'm a scientific programmer, mostly working on mathematical models and simulation. Almost all the work I do is for myself, and I have very little experience working with others' code. Many of the people I know who use Python are in similar situations. I have personally had far less trouble with tabs than with spaces (aesthetically and functionally), and it's what I'm going to continue using until my circumstances change, since Python doesn't care either way (only the community, who will never see my code).
I just think that if you're going to tell people to use spaces instead of tabs, at least explain why. It's rather inconsistent considering the author tried to avoid the issue with text editors.
Different purposes:
designing a house and developing a "real" application
vs.
learning how to use a scroll saw and how to use a programming language.
Python is a handy tool to have available. Sure, it isn't the best tool for every job, but neither is duct tape.
Sacrilege! How dare you besmirch the holy duct tape! Burn him! Burn the heretic!
I laughed at the weak who considered themselves good because they lacked claws.
Oh you think that's the hard way? Why, in my day, if we wanted to see a good Monty Python skit, we had to form our own dirt out of the elements found in the universe, and evolve our own life forms until they were advanced enough to do Monty Python skits! Set Construction? Pfft! A luxury!
Nothing to see here
At the same time, drawing up the blueprint doesn't do you any good if you don't know how to nail two boards together properly...
Nothing to see here
I've got almost 40 years in, and long ago lost count of languages, operating systems, and hardware environments.
You'll get past this stage.
You will never have any living computer language "completely understood" for any significant amount of time if you are working on anything more meaningful than simply tracking that language's implementation arc in a world of constantly changing underlying platforms.
There's a difference between learning a language and memorizing that language's commands and libraries. There's a difference between knowing a language and knowing which language features are optimally supported on a specific OS or hardware implementation, too.
Learning how you learn is the key, and I think you've already got that. Trying to learn every single thing there is to know about a computer language is a waste of time that could be better spent creating something wonderful. Instead, just learn language weaknesses and vulnerabilities, and google for syntactic boilerplate as you need it.
Hopefully you'll reach a point where you know exactly what you want to accomplish, and how that can be optimally computed in the target execution environment (regardless of whether that evironment is an embedded RISC processor or a browser DOM) and you'll plot the best path to get to that goal in whatever languages are available to you.
Eventually you'll probably start avoiding the use of any libraries at all, and start liking languages with very terse syntax. When you find yourself preferring to write fifty lines of C rather than five lines of perl that calls in 50,000 lines of code from CPAN, look out! If you don't keep that tendency well under control, you might turn into Paul Graham.
To avoid that fate, train yourself to always write code that is maintainable by people who are far less skilled than you are. That way you can delegate maintenance and enhancement to less skilled hands, and go do more interesting things yourself.
Agree. I'm always being told how wonderful/portable it is but every time I try to run a Python program I get "wrong version" or something.
Chapter 0 of the book has "Make sure you install Python 2 not Python 3.". Uhuh, there's a language I want to invest some time in. Not.
Is there a reason why the language designers didn't put some kind of versioning into their language when they took the decision that backwards compatibility wasn't important to them? Some sort of shebang on the first line with the version number...? It's not difficult.
The other setup advice, ie.: Open Edit->Preferences select the Editor tab. Change Tab width: to 4. Select (make sure a check mark is in) Insert spaces instead of tabs. Turn on "Automatic indentation" as well.
Doesn't inspire me to learn Python either. Why impose a rigid spacing structure on a language in a world where tabs aren't standardized (and never will be)?
That's only the convention the author is using. Python spacing rules are more flexible than that. If you wanted to really know them you could have googled it a long time ago. As for the rationale (again, google it?) it does make up for much readable code. I know that for some it is an idea that they cannot stomach, but readability as part of the syntax is a good think.
And as of why, have you ever had to face code with horrendous indentation or no indentation at all? Specially when people mix code with markup (oh the atrocity)? If you haven't then either you have been a lucky bastard always working with the best of programmers in eternal bliss, or you don't have much work experience at all. Newsflash: most programmers suck at writing readable code. And no, sometimes you cannot run a formatter on source code to fix the damned thing (for political and sometimes even technical reasons.)
In times like these (which are far more often that one would wish), you do end up wishing for some sort of readability function as part of the syntax.
Brackets (or whatever) aren't difficult.
And yet people still fail at writing readable code blocks and scopes with them. For that matter, if it compiles it's great, even if it is impossible to read.
I grok that Python is great for I'm-too-busy-to-learn-a-proper-language programmers to knock batch scripts together quickly but it's not a language for serious work (ie. programs that take more than a day or so to write).
It is the premier language for scientific computation and game scripting. And it has been used quite successfully in the enterprise - even if it hurts you - for writing complex applications. At this point you are just trolling and pulling arguments out of thin air just to justify your dislike for the language. I mean, it is your right to like or dislike as you please. Just don't pretend that you are being accurate, educated or objective about it.
You started with a universe having elements in it, did you?
a universe. In my day we had nothing but a singularity.
it does this. the extra credit on each exercise gives a challenge based on what the basic goal of the exercise was. I havent looked through all of these to find if there are some that are especially exciting or fun, but the chance at a bit of entry-level creativity is there.
I think that believing you'll never have to share code with others is eventually going to cause you great pain. I hope I'm wrong :-)
Oh, and vim can be configured to always use spaces, but make that completely transparent to you.
Note to ACs: I usually delete AC replies without reading them. If you want to talk to me, log in.
I have done very little programming (other than excel) since my college classes in Pascal. based on the reviews here, and the fact that the book is available online for free, I decided to give this book a try.
I have gotten to this, "Try more format characters. %r is a very useful one. It's like saying "print this no matter what". Search online for all of the Python format characters."
Well, I searched online. I went to http://docs.python.org/library/stdtypes.html and found this
Just to ask, do you really think this means much to a person who has not been involved in programming for several years?
This book is both too basic, with the instructions of "just type what you see," and too advanced, with an assumption that the reader already knows about the subject and needs no explanation beyond "go look it up somewhere"