I've been working with Troy's IbPy for a while... a great contribution
indeed. However, I wanted to get everything nailed up with Twisted
and have been spending time to do that. Fortunately, I've finally
been successful.
Troy convinced me that Qt4 was the way to go, in particular PyQt4, and
he was absolutely right. So, along the way, it was necessary to fix
Twisted's Qt reactor as it isn't part of the core distribution (some
kind of collision between Twisted's MIT and Qt's GPL). The Twisted
crew were a great help.
So, in addition to fixing the Qt reactor, I'm also hosting it and am
responsible for upkeep. I think it works well but welcome any
problems / patches anyone would like to contribute.
IbPy-Twisted now all runs in a single thread so none of the nastiness
normally associated with threads are present. Of course, the real key
is that all the goodness of Twisted is now there.
The final step was to see if Profitpy would work... and it does. It
was actually straightforward although I haven't banged on it enough to
say much more.
I have all three packages available at:
http://noc2.tarbox.org:8080/
The code itself is managed in Git but you can get tarballs of any
checkin generated on the fly (click on snapshot... you'll probably
want to stick with the head of the master branch but thats up to you)
While I realize distributed version control is a very heated topic, it
is very clear to me that Git is the way to go even with its awful
documentation and lack of proper front-ends. It'll get better... but
the core of Git is exactly right and the time spent wrestling with it
is worth it.
The Git url's can be found at the above site. I'm hosting a Git
daemon which is currently read only... if there is sufficient interest
I can fix that although with Git its mostly unnecessary. Among Git's
many strengths are its ability to forward patches using diffs Git
generates. So, anything anyone would like to contribute can be
forwarded to me via email and I'll integrate it.
-glenn
--
Glenn H. Tarbox, PhD
gl...@tarbox.org