232
|
|
|
Paul Sokolovsky |
13 years ago
|
|
|
231
|
|
|
Paul Sokolovsky |
13 years ago
|
|
|
230
|
|
|
Paul Sokolovsky |
13 years ago
|
|
|
229
|
|
|
Paul Sokolovsky |
13 years ago
|
|
|
228
|
|
|
Paul Sokolovsky |
13 years ago
|
|
|
227
|
|
|
Paul Sokolovsky |
13 years ago
|
|
|
226
|
|
|
Paul Sokolovsky |
13 years ago
|
|
|
225
|
|
|
Paul Sokolovsky |
13 years ago
|
|
|
224
|
|
Add logging set up, configuration, and use for some exceptions.
Django 1.3 has integrated support for configuring Python logging, http://docs.djangoproject.com/en/1.3/topics/logging/ . For 1.2.3, just call logging.basicConfig() directly. Set only logging level, and let it use defaults otherwise, which is timespamp-less logging to stdout. On production, that will go to Apache error.log, which has own timestamps. Later, we can make more elaborated logging set up if needed.
Also, move some hardcoded names to settings.
|
Paul Sokolovsky |
13 years ago
|
|
|
223
|
|
|
Michael Hudson |
13 years ago
|
|
|
222
|
|
|
Michael Hudson |
13 years ago
|
|
|
221
|
|
|
Michael Hudson |
13 years ago
|
|
|
220
|
|
|
Michael Hudson |
13 years ago
|
|
|
219
|
|
|
Michael Hudson |
13 years ago
|
|
|
218
|
|
|
Michael Hudson |
13 years ago
|
|
|
217
|
|
|
Michael Hudson |
13 years ago
|
|
|
216
|
|
|
Michael Hudson |
13 years ago
|
|
|
215
|
|
|
Michael Hudson |
13 years ago
|
|
|
214
|
|
|
Michael Hudson |
13 years ago
|
|
|
213
|
|
|
Michael Hudson |
13 years ago
|
|
|