IronPython represents a unique direction for developers interested in working with dynamic languages within the .NET Framework. Whether you’re looking to develop applications from scratch or add functionality and maintainability to an existing application, IronPython opens many doors while providing a high–speed, high–performance language that integrates tightly with other .NET languages.Before the book was published Alan and I exchanged a few emails, discussing duck-typing and the different audiences for IronPython in Action and Pro IronPython. In the process I ended up getting quoted in the intro to his book:
What you’ll learn
- Learn to create applications using the benefits of a dynamically typed language.
- Discover how to leverage the power of IronPython to improve existing applications.
- Explore interacting with other .NET languages by invoking the common language runtime.
Who is this book for?
- Write IronPython console and forms applications.
- Integrate IronPython scripts into existing applications to increase their functionality.
- Implement complex data patterns and interact with databases.
- Use the common language runtime to take advantage of .NET’s existing framework within IronPython scripts.
- Understand how IronPython can be brought in to solve a variety of programming tasks through extensive exercises and recipes.
- Avoid the common pitfalls of working with a dynamically typed language.
This book is designed for .NET developers interested in expanding their IronPython skills and learning how to make use of them to improve their daily programming practices. It will introduce core concepts of IronPython programming using a .NET–centric approach. Additionally, it will speak to Python developers looking to expand into their skills into the .NET world. Experience with a .NET language is expected. Previous Python experience is not necessary.
About the Author
Alan Harris is a web and application developer living in Arlington, VA. He has worked at more than a few organizations using .NET to create enterprise solutions since the glory days of version 1.1, and can still browse to some of the oldest ones. Aside from working at his desk, he spends most of his time studying Krav Maga and writing music.
"Many developers take issue with this and find the approach too loose, too error-prone. I was speaking to Pythonista and author Michael Foord about the matter; I mentioned the argument, “What if it looks like a duck, quacks like a duck, but is really a dragon impersonating a duck? You don’t want a dragon in your pond.” He replied, “if you code dragons, you’ve got no one to blame but yourself if they get in your pond.” I informed him that “the only difference between my IronPython dragons and my C# ones is my C# ones have ‘Hello my name is’ nametags.” So it goes."
I will be interested to see what you think of "Pro IronPython". I've had the luxury of reading both your book and mine, and I think you'll agree we speak to very different audiences. Apress wanted a book easy enough that someone with zero programming experience could pick it up and run, being pretty well versed by the end (which pretty much speaks to the entire Pro line I think, with a few exceptions). Your book covers some terrific stuff (the PowerShell parts I found particularly interesting) but a lot would be beyond the target audience of mine. I think, however, that they are rather complimentary books.