Stock Market Notes:

A major point of my Python adventure, is to create application(s) which will help others (and myself) try various investment scenarios. There are a lot of ways to lose/make money in stocks & options, and I've tried many of them.

The app I'm going for, will (0.1 release) grab stock quotes, & present the various covered calls for a stock graphically. If anyone has other desired features or comments, post them & (if I think they're helpful), will fold them into the app. Initial release date, end of April (think I'll beat that easily, but you know how software estimates go)

Trading wise, I had a couple of rough months starting off this year, but March went pretty well. "Went" well, since if you trade options (in the US), your month ends on the 3rd Friday of the month. If someone has a favorite option/stock combination, mention it, & that can go into the app also.

Happy Coding, Happy Trading!

Linux Tools ramblings

Checked out codecon, they have some nifty stuff going on there.

One of the things was 'monotone', a Version Control System. I was trying to get that pkg installed (onto my Ubuntu system), but kept getting this error:
./monotone-0.25-linux-x86: /usr/lib/libstdc++.so.6: version `GLIBCXX_3.4.6' not found (required by ./monotone-0.25-linux-x86)

Googled, found that a couple of people had fixed that (or nearly identical) problem, in different ways, none of which worked for me.

But then I remembered, "Hey, This is Linux", so I downloaded the source, and rebuilt it (after getting all the Boost lib dependencies downloaded & built too). I like the idea that the whole repository is stored in a single SQLite file. (easy to backup)

Long story short (too late, sorry!), monotone looks cool; I'll comment later on how it works for me.

So my current toolkit:

• Boa-Constructor (only because it somehow helped wxGlade work)
• VCS: monotone (probably subversion for Sourceforge later)
• gui-builder : wxGlade for (cross-platform) GUI construction
• Edit/IDE: PIDA ("Pida Loves you"); hey, I'm a VIM guy
• testing: probably twill, pyUnit, unittest, I'll see...
• Language: Python, of course (tried Ruby, it's too Perlish!)

Any other tools you think I'd like better? (yes, I've tried emacs)

Happy coding. (both a suggestion and a statement ;)