On Sat, Aug 22, 2009 at 3:36 PM, Graham
Dumpleton<[email protected]> wrote:
> hosting Pylons on anything besides Paste HTTP server can also be
> a problem in some cases. This is because certain setup steps for
> logging expected by Pylons applications are embedded in Paste HTTP
> server where they should not really be. This means that those magic
> steps have to be some how duplicated when using alternate WSGI hosting
> mechanisms. Such steps aren't though even documented in Pylons
> documentation, unless that has changed since last time I looked.

I guess we should just fix the implementation.  The problem is that
the logging is implemented at a different level than people think it
is.  People expect that any use of the INI file should enable logging,
but in fact it's configured in "paster serve" and "paster setup-app".
So if you load the application through loadwsgi or the entry point, or
instantiate it by hand, you have to enable the logging yourself and
that's a hassle.  We may not be able to do anything about
"instantiating it by hand" because that doesn't use an INI file, but
the other cases should arguably enable the logging.

One issue is disabling the Paster logging setup.  The other is where
to put the code instead.  It could go into paste.loadwsgi but that's
still part of Paste, and may cause compatibility problems for
non-Pylons applications.  Or it could go into Pylons itself, but since
the INI file is already parsed at that point, Pylons doesn't have it.
Although it does know what it is via config['__file'__'], so it could
go from there.  Then would there be a flag for "dont_enable_logging"?

-- 
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to