Wheee. It's 5:26am and the first rough version of the Python2C AST to Python source module is working! Yeeehaaa!

It's nice that something is working!

The bicyclerepair-general list actually had a message. Wow. I responded with lots of detail, so I probably scared the guy off. *sigh*

Now that I have a rough AST to source, I need to add the rest of the node handlers and get on to something else. I know I should clean up the source and refactor out at least the indentation code, but hey, I want to get other parts working. Hm, XP says I should refactor now while I can still understand the code. Hm.

The next piece I'll be writing is the AST search and transform code. That should be challenging, but I've had my hands deep enough in the AST that I may actually be qualified to do it.

I've also been thinking about IsExclusive. Personally, I never do raw instance variable access, but that's not necessarily true for everyone, therefore, not even self.var = value in the __init__ function is a safe bet for IsExclusive. I'll keep thinking.

Since two people have asked me if they can contribute to BRM, it's about time for me to write up the UserStories and such. When it was just me, YAGNI applied. Now it's time for enough structure to be able to delegate with a minimum of effort.

This is the first Open Source project I've worked on, so I don't know how to proceed. Do I advertise on comp.lang.python? Should I raise public awareness about a wonderful tool on the horizon? Should I wait to mention anything till there's an alpha version?

Somebody tell me, how exactly does the "release early and often" strategy apply?

Oh well, sleeptime, and more coding tomorrow.