Ben Bagert rejected the bug report "Yes, it needs to know about test.ini. It's in the projects files, so that the owner of the project may change it if desired. There is no hard coding inside Pylons itself requiring the users code to stay this way."
Therefore, supporting multiple test.ini files (for testing multiple configuration of componentes, like plugins) will not be allowed in the current Pylons? Any answer will be appreciated Agustin On 27/03/2008, Mike Orr <[EMAIL PROTECTED]> wrote: > > > On Thu, Mar 27, 2008 at 4:53 AM, 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. > > > I created a bug report for it: > http://pylonshq.com/project/pylonshq/ticket/400 > > Could you upload a "diff -u" of your change to the ticket? Thanks. > > > -- > Mike Orr <[EMAIL PROTECTED]> > > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
