So I folllowed the doc:
https://cwiki.apache.org/CLOUDSTACK/testing-with-python.html, and tried to
install marvin to my 64 bit MacBook, OS: Lion. I installed marvin.0.6.2,
and also biopython-1.59
because:
>>> import marvin
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
File "/usr/local/bin/marvin.py", line 2, in <module>
import Marvin.app.main
File "/Library/Python/2.7/site-packages/Marvin/__init__.py", line 8, in
<module>
from Marvin.primer import PrimerDesigner
File "/Library/Python/2.7/site-packages/Marvin/primer.py", line 3, in
<module>
from Bio.Seq import Seq
ImportError: No module named Bio.Seq
and wxPython2.8-osx-unicode-py2.7
because:
>>> import marvin
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
File "/usr/local/bin/marvin.py", line 2, in <module>
import Marvin.app.main
File "/Library/Python/2.7/site-packages/Marvin/app/main.py", line 2, in
<module>
import wx
ImportError: No module named wx
Next I got:
ImportError:
/usr/local/lib/wxPython-unicode-2.8.12.1/lib/python2.7/site-packages/wx-2.8-mac-unicode/wx/_core_.so:
no appropriate 64-bit architecture (see "man python" for running in 32-bit
mode)
After googling, I was told that wxPython on Mac is only available in 32-bit
mode, and this link (
http://stackoverflow.com/questions/2565201/wxpython-incompatible-with-snow-leopard)
suggests to run python in 32 bit mode.
My question to you guys is: am I on the right path so far? Should I run
python marvin in 32 bit python mode? Any suggestions?
Thanks.
Yichi
On Tue, Sep 18, 2012 at 7:50 AM, David Nalley <da...@gnsa.us> wrote:
> On Mon, Sep 17, 2012 at 7:24 PM, Edison Su <edison...@citrix.com> wrote:
> > First, thanks for working on test stuff, we really need more automate
> test cases.
> > If you plan to work on the API test, we have a python test framework:
> https://cwiki.apache.org/CLOUDSTACK/testing-with-python.html. The most
> compelling feature is that it supports code completion for cloudstack API,
> very easy to write test case in Eclipse environment. And we are setting up
> a test infrastructure, which will execute all the test cases written for
> this framework.
> > We already have around 500+ test cases, or maybe more, but apparently
> it's not enough. If you like to work on it, that will be great!
> >
>
> While I like the functional/integration tests, as you note we have
> 500+ currently. Those tests also take many hours to run at present.
> Unit tests should be something fast, a sanity check, and we only have
> 25 right now for the entire code base, so while I like
> func/integration tests, I'd really like for our unit tests to be
> runnable on every commit, and provide some decent level of coverage so
> that we have a bit of confidence that code works well, and provide
> good feedback to folks on whether their commit passes the sniff test.
>
> --David
>
>
