Spring Python is cooking!

Spring Python is growing fast and I’m excited to be working on this project. I just wanted to list some of the things that shows the many ways this is happening.

First of all, I must point out that we just recently released version 0.8.0. This version contains the newly rewritten IoC container as well as changing from “component” to “object” in the classes and APIs. By separating object configuration from object creation, we have been able to write multiple parser including: the legacy PyContainer format, a new XML format custom built for Spring Python, Spring’s 2.5 XML format, and also a pure python @Object format. We can also reference between input sources with ease.

This release counts as the fourth one made since Spring Python became an official extension back in July. We have made at least one release per month, which if you check out JIRA, will see is current target pace leading up to version 1.0.0. A steady release cycle is a good sign of an active project.

I also have enjoyed answering questions posted in the community forum. I was really excited to be able to help a user who was experimenting with changes to ai4game, a pygame application. He wanted to wrap some objects with AOP. First of all, thanks to this user, we uncovered a bug in Spring Python, and I managed to code the patch immediately and get it out to this user. I like real-world examples because they show me what types of problems people are trying to solve and it also lets me know people are really using this software. It also helps expose bugs and grow the reliability of things.

Another things I’m really excited about is about this year’s Spring One Americas conference. Spring Python is scheduled for a presentation titled Introduction to Spring Python. Even if I’m talking to a relatively empty room, I will be excited to do that.

Also, seeing Russ getting out the word during his presentation at the London Spring Users Group was fantastic!

All of these things make me really glad to be working on Spring Python.

Leave a Reply

Your email address will not be published. Required fields are marked *