Slashdot Mirror
The Python Cookbook
Beautiful plumage. O'Reilly, fortunately, has all kinds of experience with animals.
The Python Cookbook consists of seventeen chapters that contain between eight and twenty-six individual recipes. Chapters and recipes are roughly ordered by increasing complexity, length, and required background knowledge, starting with the simple "Swapping Values Without Using a Temporary Variable" and ending with the complete module "Parsing a String into a Date/Time Object Portably." The chapters are mostly organized by subject -- "Text," "Files," "Object-Orientated Programming," "User Interfaces" -- but also include "Python Shortcuts" and "System Administration." The background required varies: Whereas the chapter on "Text" starts off with Fred L. Drake reviewing the most basic string operations such as slicing and concatenation, Paul F. Dubois can only sketch the core concepts of lexing and parsing in "Programs About Programs."
This of course is a hallmark of all cookbooks, programming- or food-wise: Nobody will like everything, but everybody will like something. The worst fragmentation occurs, as expected, between examples of Python 1.5.2 and Python 2.2. Most recipes give preference to one version, and then point out how the problem could have been solved in the other version. This is more useful than the code that was written for all versions, because it gives a deeper insight into the changes that Python has gone through. The result is that after a few chapters, you start wondering why anybody in their right mind would keep using Python 1.5.2 instead of 2.2.* with its iterators, list comprehensions, new classes, and expanded module library.
Martelli and Ascher have done a good job balancing the different forms. Only one chapter struck me as lopsided: "System Administration", where ten of the sixteen recipes are Windows-only. Even though there is a good reason for this -- Microsoft's native administration tools just aren't like those provided with Unix -- the editors might want to rethink the selection of recipes in this chapter for future editions.
Generally helpful. The "Python Cookbook" has helped me in three ways. First, I found quite a lot of the examples themselves, especially those in the chapters "Python Shortcuts" and "Object-Orientated Programming" useful for everyday work. Second, reading more than 500 pages of peer-reviewed and well-commented code gave me a greater feeling for common idioms and constructs that are rare in this clarity in wild-type code. However, the book is strongest when more general principles of "Pythonic" programming are discussed, for example when Martelli demonstrates the merits of the "Look Before You Leap," "Easier to Ask Forgiveness than Permission," and "Homogenize Different Cases" methods.
My favorite recipe is Sebastien Keim's "Implementing a Ring Buffer," where an object carries a class deep in its bowels, and changes into this class in a rather cool Dr.-Jekyll-to-Mr.-Hyde transformation on the fly. The one recipe I found downright evil was "Sending HTML Mail," which should have been implemented as "Turning HTML Mail into Plain Text" with a note on how people who send HTML mail are going to be the first against the wall when the revolution comes. The best quote in the book comes from Tim Peters: "We read Knuth so you don't have to" -- Python's promise of programming power for the people, expressed in (dare I say it) a nutshell.
Conclusion:
I can recommend the "Python Cookbook" wholeheartedly to anyone who has passed into the advanced stage of language learning and is willing to actually sit down and work through the code. Anybody who is looking for a deeper understanding of Python, solutions to common coding problems, or starting points for their own projects will also profit. This book should have RedHat customers hammering at the gates of Raleigh, demanding the power of iterators and list comprehensions that their SuSE counterparts already enjoy by default; it demonstrates the superiority of Python 2.2.* over 1.5.2 in great detail.
Because of this, however, my guess is that 2.2.* will quickly replace 1.5.2, turning large parts of this book into historical footnotes in two years at the latest. This is no fault of O'Reilly's, but rather a current fact of Python life. The editors have done a good job of nailing the parrot, and until this Pythonic Norwegian Blue does the inevitable backflip, it should give its owner much pleasure.
You can purchase The Python Cookbook from bn.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.
The title "Python Cookbook" has gotta look weird to people bopping around Barnes & Noble who aren't in the know. :)
/*drunk.. fix later*/
And for those of you that can't get your hands on a python, the adder, asp, boa, cobra, diamondback, etc cookbooks are just as well packed with tasty recipes.
"Accept that some days you are the pigeon, and some days you are the statue." - David Brent, Wernham Hogg
And here I was hoping for the recipe for crunchy frog.
Kierthos
Mr. Hu is not a ninja.
Or, as Homer might add: "...mmm...python"
Athletic Scholarships to universities make as much sense as academic scholarships to sports teams.
Cornmeal Crusted Rattle Snake with Cactus-Corn Succotash
Recipe courtesy Joey Altman, Copyright 2001
2 1/2 pounds rattle snake, dead
1 cup buttermilk
1 cup cornmeal
1 cup flour
1 tablespoon salt
1 tablespoon chile powder
1 tablespoon garlic powder
1 tablespoon paprika
1 teaspoon cayenne pepper
1 teaspoon ground cumin
1 cup vegetable oil
Cactus-Corn Succotash, recipe follows
Using a sharp boning knife remove the meat from the snake by cutting down the back, just slightly to 1 side of the spine from the head to the rattle. Using the tip of the knife peel the meat from the ?rib cage?. Once you removed the 2 long strips of meat, lightly pound them with the back of the knife to tenderize them. Cut the strips of meat into 1-inch pieces and place in a bowl with the buttermilk. Mix to coat well. In a large bowl combine the cornmeal with the flour and the spices. Heat the oil in a large skillet on medium high heat. Dredge the snake pieces in the flour mixture and fry for 2 minutes or until golden brown and then transfer to a paper towel lined plate. Repeat until all the snake pieces are cooked. Serve with Cactus-Corn Succotash.
Cactus-corn succotash:
2 tablespoons olive oil
1 cactus pad, thorns scraped off, cut into small dice
2 ears corn, shucked
1 red onion, peeled, sliced in rings, grilled with olive oil and chopped in small dice
1 bunch scallions, grilled and chopped
1 chayote squash, sliced 1/4-inch thick, grilled with olive oil and chopped in small dice
1 tablespoon minced garlic
2 tablespoons minced jalape?o
1/2 cup diced red bell pepper
4 tablespoons butter
1 cup chicken stock
1 cup diced, peeled and seeded tomatoes
1/2 cup chopped cilantro
Salt and pepper
Grilling the vegetables first gives another great layer of flavor, however, it is not absolutely necessary. Just omit that step and cook the vegetable right in the pan. In a skillet on high heat saute the vegetables except the tomatoes in the olive oil for 2 minutes. Add the stock and butter and cook until mixture reduces by half. Add tomatoes and seasoning and serve with the warm snake ?nuggets? on top.
Yield: 4 servings
Prep Time: 30 minutes
Cook Time: 10 minutes
Difficulty: Medium
Pythons? I heard they taste like chicken!
[alk]
The perfect companion piece to Bake a Snake.
daed si luap
No no he's not dead, he's, he's restin'! Remarkable bird, the Norwegian Blue, idn'it, ay? Beautiful plumage!
Yeah, like the guy who drew Tux, whatshisname..
Escher was the first MC and Giger invented the HR department.
Thanks! You just made me laugh out loud, and that's always fun.
Having to use a debugger at all is a sign that the code doesn't clearly express what it's going to do.
No, it's a sign that the code isn't doing what you want it to do. Sometimes that's due to a flaw in your code. Sometimes it might even be due to something else, like an API call that doesn't do what you expect, or even an API call that is downright buggy.
It's as silly to say that one should never need a debugger, as to say that one cannot do without a debugger.
a debugger that can't even tell you which expression is about to be evaluated
So, when you have a project on a platform with primitive development tools, what do you do? Refuse to work on the project?
Tell me, what development tools do you use? They must be wonderful. Maybe I should use them.
steveha
lf(1): it's like ls(1) but sorts filenames by extension, tersely