On Fri, 16 May 2014 13:08:17 +0200 Thomas Guettler email@example.com wrote:
Am 16.05.2014 11:54, schrieb Antoine Pitrou:
On Fri, 16 May 2014 11:32:55 +0200 Jonas Wielicki firstname.lastname@example.org wrote:
On 16.05.2014 11:27, Antoine Pitrou wrote:
On Fri, 16 May 2014 09:05:11 +0200 Thomas Güttler email@example.com wrote:
I think the following solution is very flexible and solves most needs to set up logging, since I can implement your needs in for example your_environment_module.set_up()
This looks dubious to me. There is no reason to have a shared Python logging configuration, IMO. Also, I don't understand why this is importing a module.
While I agree that importing a module might not be the right way, having a standard way to configure logging via environment variables might be helpful.
I entirely disagree. An environment variable is a very lousy way to specify a configuration file's location; and there is no reason to have a common logging configuration for all Python applications.
** I don't want a common logging configuration **
I want a standard hook to find the logging configuration.
Why would that be Python's business? If the hook is meant to be truly "standard", then it should be something like a LSB standard.
End users don't really care whether some application is written in Python or another language. Why a Python-specific hook? What do users gain?
And I want it to be a Python method.
Basically you are telling us what /you/ want, but not why it would be useful for the broader community.