On Mon, Jun 29, 2009 at 11:38 AM, Ben Bangert<[email protected]> wrote: > > On Jun 29, 2009, at 10:35 AM, Ben Bangert wrote: > >> The request specific globals are Stacked object proxies to resolve the >> issue, however if they have the same config, its possible that since >> the loading of the app occurs *before* any request is actually >> received, they both end up using the same global config object thats >> created at load-time. I believe that is what is occurring in this >> case. > > Ok, I've pushed a patch to the Pylons 0.9.7.x branch that should make > it possible to setup multiple Pylons apps in the same process. From my > testing, it doesn't seem to affect existing apps, but new/existing > Pylons apps that want to be nested will need to make a few minor > changes to allow them to be nested (and avoid using the process-wide > global config).
This should probably be standard in the next version of Pylons. Making a config and returning it makes more sense than using the global config in load_environment., and would also help in test fixtures and other edge cases that don't want to deal with the globals. -- Mike Orr <[email protected]> --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-discuss" 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/pylons-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
