Open Source Health Information Platform

OSHIP Python 2.6 compatible?

Asked by Justin Duperre

I am getting a lot of errors trying to get this up and running. I read somewhere that OSHIP is only compatible with Python 2.5 since 'with' is now a protected word in 2.6 (I think?)

Here are some errors I am getting, there are 33 of them (from bin/test): I do have C/C++ compilers installed, and I followed the directions exactly for installing on ubuntu.

File "/home/hfoss/oship/oship/src/oship/openehr/tests/composition.txt", line 54, in composition.txt
Failed example:
    IComposition.providedBy(composition)
Exception raised:
    Traceback (most recent call last):
      File "/home/hfoss/oship/oship/eggs/zope.testing-3.8.3-py2.6.egg/zope/testing/doctest.py", line 1361, in __run
        compileflags, 1) in test.globs
      File "<doctest composition.txt[line 54, example 42]>", line 1, in <module>
        IComposition.providedBy(composition)
    NameError: name 'IComposition' is not defined

edit; i forgot to introduce myself

my name is Justin, i am a student at western new england college in Springfield, Massachusetts. we are forming a new software engineering course that integrates open source software with engineering concepts. several students are investigating and setting up different projects in our development environment - i picked oship. our main focus is hfoss - humanitarian free and open source software.

i am forming a tutorial for setting up oship, located here at our homepage; http://www.xcitegroup.org/softhum/doku.php?id=oship
its a little out of order right now, but any comments would be great. just trying to get a dev environment for oship going.

thanks

Question information

Language:
English Edit question
Status:
Answered
For:
Open Source Health Information Platform Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
Roger Erens (rogererens) said : 		#1

Hi Justin,

at the moment, your best bet might be to use the stable branch or maybe a somewhat older release of the oship (main) branch, e.g. -r 388. I'll have a closer look this weekend.

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

Hi Roger,

Thanks for the reply. I have tried installing the stable branch and it hangs up on the egenix install, even though I installed it manually. I am going to clean everything off and go through the installation instructions again on oship.org - the instructions there are a little different than here.

Revision history for this message
Roger Erens (rogererens) said : 		#3

Hi Justin,

the egenix installation ought to be independent of the branch you try to install.
As an extra precaution, I would advise you to create a virtual machine using software like VirtualBox or VMWare's and install Ubuntu OS afresh on that.
I had another round of editing of oship.org's installation instructions based on your document. Thanks and keep us posted!

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

Hi Roger,

Will do!
We currently have a VMWare Web Panel set up to create virtual machines. I am still having these test errors while following the directions on oship.org. I am going to wipe the virtual machine clean and start from the beginning. I think i am getting some problems during the "$(oshipenv)python setup.py install" step. It looks like the script is halting because I have martian .12 when the version needs to be >=.10, <.12

Could this be the problem?

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

Roger, I found this in the archives:

http://<email address hidden>/msg00915.html

This looks like the problem I am having.

I am going to wipe out the VM and do a clean install, I may not have installed oship in oshipenv, by accident.

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

Update:

  Ran 33 tests with 3 failures and 0 errors in 0.361 seconds.
  Tear down zope.testing.testrunner.layer.UnitTests in 0.000 seconds.

Tests with failures:
   /home/hfoss/oshipenv/oship/oship/src/oship/openehr/tests/extract.txt
   /home/hfoss/oshipenv/oship/oship/src/oship/openehr/tests/integration.txt
   /home/hfoss/oshipenv/oship/oship/src/oship/openehr/tests/datastructure.txt
Total: 42 tests, 3 failures, 0 errors in 9.057 seconds.

are these typical?

Revision history for this message
Roger Erens (rogererens) said : 		#7

Eduardo,

can you answer this?

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

These errors don't really make sense. One example is in datastructure.txt.
It says IElement(element1) , element1 is not defined. I took a look at the script and it is defined in several places.
I tried running the server anyways and it appears to look OK.

Revision history for this message
Roger Erens (rogererens) said : 		#9

> JustinD gave more information on the question:
> These errors don't really make sense. One example is in datastructure.txt.
> It says IElement(element1) , element1 is not defined. I took a look at the script and it is defined in several places.

Yeah, well, we're just at the beginning of improving the quality of
the code using these kind of tests. We have to go through a learning
curve.

> I tried running the server anyways and it appears to look OK.

Good; so it was a matter of starting with a clean slate?

Roger

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

Yup. I will now test out some applications. Thanks for the support Roger!

Revision history for this message
Eduardo Ribeiro (eduardo.cesar) said : 		#11

Hi Justin and Roger,

We are in a process of redefining the internal structure of parts of OSHIP, because specific issues showed up (e. g. circular importing) in some modules.

But in response to that particular question Roger, no, that was another error, unrelated with this one.
It seems that we forgot to update the tests.

I took a look in datastructure.txt and integration and corrected the errors. In this process, I discovered some parts of code that we had not updated to reflect the original changes too, that possibly would couse some breaks in the future.

Thank you Justin for pointing this out. :)

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

Your welcome, thank you for the support as well Eduardo!

I have a correction for the installation instructions posted on oship.org, for Ubuntu 9.10:

installing libxslt/libxml the correct command is: sudo apt-get install libxslt1-dev

this installs both libxslt and libxml2 (libxml2 as a dependency).

Revision history for this message
Roger Erens (rogererens) said : 		#13

Thanks Justin,

I knew it had to be something like that, but had not gotten around to
dig back into it.

...
> I have a correction for the installation instructions posted on
> oship.org, for Ubuntu 9.10:
>
> installing libxslt/libxml the correct command is:  sudo apt-get install
> libxslt1-dev
>
> this installs both libxslt and libxml2 (libxml2 as a dependency).

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.