On Jan 4, 2008 5:36 PM, Tim Black <[EMAIL PROTECTED]> wrote: > > Diez B. Roggisch wrote: > Tim Black schrieb: > > I get this error too. I found this fix > http://trac.turbogears.org/changeset/2108 which has already been applied > in the version of TurboGears which I have installed (1.0.3.2), so > evidently it doesn't fix the problem. I'm using nose-0.10.0-py2.5.egg. > Anyone have a fix or recommendation? > > I had difficulties with easy_installing ConfigObj. For whatever reason, > it grabbed a broken version that didn't do anything usefule at all. > > So I fetched the egg myself & easy_installed it by hand, fulfilling the > dependency. Then things worked. > > Thank you. I tried your suggestion but it didn't work because I'm on > Python 2.5. > > TurboGears only lists ConfigObj 4.3.1 and 4.3.2 as possible versions to use > on http://www.turbogears.org/download/filelist.html, and they are only > listed for Python 2.3 and 2.4. TurboGears recommends using Python 2.5 now, > so I'm using it in a virtualenv setup. For Python 2.5 I can only find > ConfigObj 4.4.0, which is what is installed on my machine and apparently > generates the error. So, does anyone know whether TurboGears 1.0.3.2 (or > 1.0.4b3) is compatible with ConfigObj 4.4.0? Or is there a ConfigObj 4.3.1 > or 4.3.2 for Python 2.5? Or should I downgrade to Python 2.4?
Well, on Ubuntu (Dapper) with the Python 2.4, TurboGears-1.0.4b3-py2.4.egg and a newly fetched ConfigObj-4.3.1-py2.4.egg I'm still getting the "cannot import name config" error. -- Ubuntu Linux DC LoCo Washington, DC http://dc.ubuntu-us.org/ --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/turbogears?hl=en -~----------~----~----~----~------~----~------~--~---
