import after install generates error (w/trace)

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Try to install foresite following install directions(I am on mac osx
tiger but it should happen on any os)
2.
3.

What is the expected output? What do you see instead?
after installation open python. Then write "from foresite import *".
Should install gracefully.
Actually responds with the following trace:
++++++++++++++++++++++++++++++++++++
Traceback (most recent call last):
  File "<stdin>", line 1, in ?
  File
"/opt/local/lib/python2.4/site-packages/foresite-0.9-py2.4.egg/foresite/__init__
.py",
line 16, in ?
    from serializer import *
  File
"/opt/local/lib/python2.4/site-packages/foresite-0.9-py2.4.egg/foresite/serializ
er.py",
line 6, in ?
    from utils import gen_uuid, generateAtomContent
ImportError: cannot import name generateAtomContent
++++++++++++++++++++++++++++++++++++

FIX: remove the import generateAtomContent line from serializer.py. Its
never used and never defined. 

What version of the product are you using? On what operating system?
current version as of 10/08. Operation system, Mac OSX tiger

Please provide any additional information below.
I hope this project works besides this, 'cause I could sure use it.

Original issue reported on code.google.com by jgron...@gmail.com on 30 Oct 2008 at 11:49

[GoogleCodeExporter]

Also, I was using the python version. The fix allowed it to compile but the 
library
doesn't work on importing the resource given in the example. 

"http://www.openarchives.org/ore/0.9/atom-examples/atom_dlib_maxi.atom"

Original comment by jgron...@gmail.com on 31 Oct 2008 at 6:27

[GoogleCodeExporter]

Fixed. generateAtomContent should be the longer but slightly more descriptive:
build_html_atom_content

The code now parses 1.0 atom, rather than 0.9 atom, by default.  If you need to 
work
with 0.9, then there's OldAtomParser and OldAtomSerializer.

Original comment by azarot...@gmail.com on 1 Dec 2008 at 5:00

• Changed state: Fixed