731212 - Refactor logging code for Django 1.5

Status: RESOLVED INVALID

(developer.mozilla.org :: Security, defect)

Description

[Luke Crouch [:groovecoder]]

our existing
logging facility conflicts with the one available as of Django 1.3. We
use a setting named LOGGING for this, which is a dictionary of
configuration for our logging; Django 1.3 also uses a setting named
LOGGING for this, and bails when it can't find the appropriate keys in
the dictionary for how Django's built-in logging is configured.

Fixing this one is trickier; our options here are to switch over to
Django's native logging support, or rewrite a bit so that we use a way
of configuring our logging that doesn't clash with Django.

When I ran out of testing time, I was taking the first option there,
and just setting up a logging config that matches Django's expected
format. The test suite was still unable to bootstrap, though.

Comment 1

[James Socol [:jsocol, :james]]

Aren't we just using python's logging module?

Comment 2

[Luke Crouch [:groovecoder]]

James can you stick a p=<hours> estimate on this?

Comment 3

[John Karahalis [:openjck]]

Django 15 -> Django 1.5. Getting ahead of myself here.

Comment 4

[James Bennett [:ubernostrum]]

This branch refactors everything except the celery logging, which we don't seem to actually be using at the moment. Once we do use it, we can put it back in:

https://github.com/ubernostrum/kuma/tree/logging-refactor

Comment 5

[James Bennett [:ubernostrum]]

(though, for obvious reasons, it can't merge until we're at switch-flipping time)

Comment 6

[John Karahalis [:openjck]]

Tracking this as a subtask in Kanbanery.