It uses PyQwt... and, of course, Qt... but it "just worked" for me, I
think... although qwt "might" have required some tinkering IIRC.
-glenn
>
> Thanks,
> Tavi
> >
--
Glenn H. Tarbox, PhD || 206-494-0819 || gl...@tarbox.org
"Don't worry about people stealing your ideas. If your ideas are any
good you'll have to ram them down peoples throats" -- Howard Aiken
What version of Qt/PyQt? You should use 4.4 if you can.
> Do I have to install pyqwt/qt from sources?
That would be best.
I just ran into this bug... on Windows. It looks like something isn't
generated correctly via pyuic4. I'll either work around it in the ui
file or find the underlying bug. In both cases, I'll let you know
about a permanent fix.
In the mean time, just open up ui_callableselect.py (not ui) and
comment out every line that begins "self.callableType.addItem(icon".
Looks like it's been fixed, just not in a release (I can certainly sympathize :)
http://www.mail-archive.com/py...@riverbankcomputing.com/msg14281.html
You'll need scipy, too.
> How do I do backtesting?
Connect to TWS, let it run for a while, then save the session. Close
the profit device and restart it. Load your strategy (you're on your
own here -- use the shell), then import your saved session. The tool
will re-send each TWS message thru the system and your code can pick
them up.
You can also use the same approach without saving a session -- load
your code, then connect to the demo TWS. As the app creates message
objects, your code can react by placing orders (or doing whatever it
is that you want).
> Where does it get the historical data?
From previous sessions. You have to save them yourself.
> Do I need an IB account to use a particular feature? Can I do anything
> without an IB account?
You can use the demo account. Both edemo and fdemo accounts work.
> I guess a better question would be if there is an user's manual
> somewhere?
Patches welcome. :)
What revision of profitpy and ibpy? In both cases, update to the
latest sources if you can.