Finally the problem is resolved with this patch in tests/__init__.py
original line 31, tests/__init__.py
test_file = os.path.join(conf_dir, 'test.ini')
cmd = paste.script.appinstall.SetupCommand('setup-app')
cmd.run([test_file])
class TestController(TestCase):
def __init__(self, *args, **kwargs):
wsgiapp = loadapp('config:test.ini', relative_to=conf_dir)
self.app = paste.fixture.TestApp(wsgiapp)
TestCase.__init__(self, *args, **kwargs)
patched line 31, tests/__init__.py
from pylons import config
config_filename = config["global_conf"]["__file__"]
test_file = os.path.join(conf_dir, config_filename)
cmd = paste.script.appinstall.SetupCommand('setup-app')
cmd.run([test_file])
class TestController(TestCase):
def __init__(self, *args, **kwargs):
wsgiapp = loadapp('config:%s' % config_filename,
relative_to=conf_dir)
self.app = paste.fixture.TestApp(wsgiapp)
TestCase.__init__(self, *args, **kwargs)
Hopefully, this patch will be integrated in Pylons 9.7 :), to allow the
correct behavior ofpylons' nose plugin
On 27/03/2008, avillena <[EMAIL PROTECTED]> wrote:
>
>
> Hi!
> At work we are working in a composite we application composed by
> many pugings, echa with their own bunch orf dependencies. Therefore,
> we want to manage several test_plugin_name_here.ini files.
> Using the pylons' nose pluging seemed to be the right answer, sisce
> it allows to indicate the specific ini file that you want to use . But
> in some place within pylons own files or the module generated code the
> "test.ini" is harcoded.
>
> Any hint?
>
> Thanks
>
> Agustin
>
> PD: patching the generated tests/__init__.py to recognize the given
> configuration file only worked in some cases, but the hardcoded
> test.ini remains somewhere
>
> original line 31 of tests/__init__.py
>
> test_file = os.path.join(conf_dir, 'test.ini')
>
> patch
>
> from pylons import config
> config_filename = config["global_conf"]["__file__"]
> test_file = os.path.join(conf_dir, config_filename)
>
>
> >
>
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
