Pedro Silva wrote:
Didn't work with python 2.6, giving out the same stack trace.
We're still working on 2.6 support, so I can't guarantee that the eggs we built for 2.6 are functional. Best to stick with 2.5 for now.
However, it did work with python 2.5, as far as I can tell. Thanks for your help! I guess it had something to do with certain python bytecode pre-compiled for a different architecture/machine/etc.?
If built on the same platform, the bytecode would be the same, but built with 2.6 it could've been different (and it appears that was the case).
I will starting testing now, and hope to be able to contribute something in the future.
Great, thanks!
--nate