Ok, After some reflection, I figured out what was going on. One of my __init__.py's was loading the TG2 version of dbmechanic. (which required all of the tg2 and pylons stuff)
This has since been remedied, with the result being that it is a slightly longer import statement for tg2. This creates more consistency however, and I see it as a good thing. To be absolutely clear, dbmechanic uses the TG1 expose, validate and error handler. The trunk is updated, I will create a release very soon. (0.2b1r225) -chris On Feb 8, 9:27 am, Christoph Zwerschke <[EMAIL PROTECTED]> wrote: > percious schrieb: > > > No need to have pylons if you are just doing TG 1.0. > > > If you get some error message without having pylons let me know. > > I may have forgotten to get rid of an import or something. > > The problem is that dbmechanic needs TG 2.0 since it does things like: > from tg import expose, validate > > Not sure whether you could TG 1.0 as well, but for TG 1.0 you must > import from "turbogears" instead from "tg". > > So with the current version of dbmechanic you need to install TG 2.0, > and this in turn means installing Pylons and its dependencies which you > wouldn't need for TG 1.0. > > -- Christoph --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
