Hi Ben Maybe I have explain it better.
Since we need to maintain several test.ini (one for each configuration os our system), we saw the pylons' nose plugin's parameter as the solution. But soon we found that the nose plugin's parameter is irrelevant because the default "test.ini" is hardcoded in tests/__init.py__ We "fixed" tests/__init.py__ to support the nose plugin's parameter retrieving the current configuration file from pylons' config object. The resulting patch is attached, Is this patch has some value, It maybe integrated in pylons 0.9.7 Good luck Agustin On 28/03/2008, Ben Bangert <[EMAIL PROTECTED]> wrote: > > On Mar 28, 2008, at 4:50 PM, Agustin Villena wrote: > > > Therefore, supporting multiple test.ini files (for testing multiple > > configuration of componentes, like plugins) will not be allowed in > > the current Pylons? > > > I don't understand what you mean that its not allowed in Pylons. It's > in *your* project, *your* files. The default is to use test.ini, but > you can change it to use anything you want, Pylons has nothing to do > with that except it dropped that default in there to begin with. > > The Pylons nose plugin specifically takes an ini option that you can > provide on your own to nose. --with-pylons=TEST.INI, or whatever one > you want to use. The only change I can think of that might make it > easier in Pylons is if the test/__init__.py was able to figure out > what option you had specified to --with-pylons, though I'm unsure how > to get that info at the moment. > > Cheers, > > Ben > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-devel" group. To post to this group, send email to pylons-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/pylons-devel?hl=en -~----------~----~----~----~------~----~------~--~---
multi_test.patch
Description: Binary data
