Diez B. Roggisch wrote: >> I can think of some solutions, but they're a bit involved, and I >> presume I'm not the first person to come across this. Is there a >> canonical way of doing this that I've missed? >> > > Several. I do this: > > - passing callables for the options > > - limiting nosetests via -w to the <projectname>/tests module > > - protecting the aforementioned callables with request_avialable, and return > dummy-data if not true. > I had the same issue with nosetests trying to load the whole world before it even exists.
Re: "a bit involved" I've found that, when adding sqlalchemy autoloading with multiple mysql+postgres databases to the case above, a serious Goldberg contraption (*) is needed, in order to achieve schema and model creation/population/destruction/testing in the way others do with "tg-admin sql create" and "nostests" I would love to give out some advice and best practices, but I'm not there yet. (*) http://en.wikipedia.org/wiki/Rube_Goldberg_machine --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
