Asked by Justin Duperre

Hello everyone,

Is there a reason why Pyclips is not installed via buildout for oship 2.0 and epis3? (It is for the stable version)

I keep getting this error during bin/test:

ImportError: No module named _clips

I noticed in the buildout.cfg for oship 2.0 and epis3 do not install pyclips.

EDIT: I do have C compiler installed (sudo apt-get install build-essential)

Bottom line is stable version runs fine with demos, but I am unable to run epis3 or demo apps on oship 2.0.

Would an alternative solution be to move epis3 templates and python files to the 'src' file of the stable oship?



Question information

English Edit question
Open Source Health Information Platform Edit question
No assignee Edit question
Last query:
Last reply:
Revision history for this message
Diego Manhães Pinheiro (dmpinheiro) said :

In fact, in version 2.0 and epis3 you have to install the PyClips manually using a virtualenv environment. Actually, there is a problem with the installation process found at FAQ. It doesn't cover this part of the process.
At the moment, i'm working on a few installation improvements, like install PyClips automatically via buildout. The trunk version will benefit with these improvements. In a few days, all the installation process will be updated.

Revision history for this message
Justin Duperre (jduperre) said :

Ok thanks, I tried adding it into the buildout.cfg file but it didn't quite work. I probably missed something.

Can you help with this problem?

Provide an answer of your own, or ask Justin Duperre for more information if necessary.

To post a message you must log in.