blocks|key|328007|text|我目前使用的是我自己创建的日志系统。使用CSV格式进行日志记录。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|328008|django-csvlog|offset|length|328009|这个项目仍然没有完整的文档，但我正在努力。|328010|entityMap|0|LINK|mutability|MUTABLE|url|http://bitbucket.org/oduvan/django-csvlog/^0|0|0|D|0|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Q|8|@]|9|@$D|R|E|S|1|T]]|A|$]]|$1|F|3|G|5|6|7|U|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|V|8|@]|9|@]|A|$]]]|I|$J|$5|K|L|M|A|$N|O]]]]

I am currently using a logging system, which I created myself. It uses CSV format for logging.

<a href="http://bitbucket.org/oduvan/django-csvlog/" rel="nofollow noreferrer">django-csvlog</a>

This project still doesn't have full documentation, but I am working on it.

blocks|key|330447|text|到目前为止，我找到的最好的方法是在settings.py中初始化日志设置。您可以使用配置文件，也可以一步一步地以编程方式完成-这取决于您的要求。关键是，我通常会将我想要的处理程序添加到根记录器中，使用级别，有时使用logging.Filters来将我想要的事件添加到适当的文件、控制台、syslog等。当然，您也可以将处理程序添加到任何其他记录器，但在我的经验中通常不需要这样做。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|330448|在每个模块中，我使用以下命令定义一个记录器|330449|logger+=+logging.getLogger(__name__)|code-block|syntax|javascript|330450|并使用它来记录模块中的事件(如果我想进一步区分的话)，使用一个记录器，它是上面创建的记录器的子级。|330451|如果我的应用程序可能会在没有配置settings.py日志的站点中使用，我会在某个地方定义一个NullHandler，如下所示：|330452|#someutils.py

class+NullHandler(logging.Handler):
++++def+emit(self,+record):
++++++++pass

null_handler+=+NullHandler()|330453|并确保它的一个实例被添加到我的应用程序中使用日志记录的模块中创建的所有记录器。(注意:+NullHandler已经在Python3.1的日志记录包中，并将在Python2.7中。)所以：|330454|logger+=+logging.getLogger(__name__)
logger.addHandler(someutils.null_handler)|330455|这样做是为了确保您的模块在没有在settings.py中配置日志记录的站点中运行良好，并且不会收到任何令人讨厌的"No+handlers+be+found+for+logger+X.Y.Z“消息(这是关于可能配置错误的日志记录的警告)。|330456|这样做符合您声明的要求：|330457|与当前一样，您可以为不同的事件设置不同的日志处理程序。使用适用于命令行模块的getLogger(__name__).|offset|length|style|CODE|330458|Easily，可以轻松访问模块中的日志记录程序(|unordered-list-item|330459|
|330460|Easy+access+to+loggers+)-它们也会导入日志记录程序|330461|330462|更新：请注意，从1.3版开始，Django现在包含了support+for+logging。|BOLD|330463|entityMap|0|LINK|mutability|MUTABLE|url|https://docs.djangoproject.com/en/dev/topics/logging/^0|0|0|0|0|0|0|0|0|0|0|12|J|0|0|0|0|0|0|3|Q|J|0|0^^$0|@$1|2|3|4|5|6|7|1L|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|1M|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|1N|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|1O|8|@]|9|@]|A|$]]|$1|K|3|L|5|6|7|1P|8|@]|9|@]|A|$]]|$1|M|3|N|5|F|7|1Q|8|@]|9|@]|A|$G|H]]|$1|O|3|P|5|6|7|1R|8|@]|9|@]|A|$]]|$1|Q|3|R|5|F|7|1S|8|@]|9|@]|A|$G|H]]|$1|S|3|T|5|6|7|1T|8|@]|9|@]|A|$]]|$1|U|3|V|5|6|7|1U|8|@]|9|@]|A|$]]|$1|W|3|X|5|6|7|1V|8|@$Y|1W|Z|1X|10|11]]|9|@]|A|$]]|$1|12|3|13|5|14|7|1Y|8|@]|9|@]|A|$]]|$1|15|3|16|5|6|7|1Z|8|@]|9|@]|A|$]]|$1|17|3|18|5|14|7|20|8|@]|9|@]|A|$]]|$1|19|3|-4|5|6|7|21|8|@]|9|@]|A|$]]|$1|1A|3|1B|5|6|7|22|8|@$Y|23|Z|24|10|1C]]|9|@$Y|25|Z|26|1|27]]|A|$]]|$1|1D|3|-4|5|6|7|28|8|@]|9|@]|A|$]]]|1E|$1F|$5|1G|1H|1I|A|$1J|1K]]]]

The best way I've found so far is to initialize logging setup in settings.py - nowhere else. You can either use a configuration file or do it programmatically step-by-step - it just depends on your requirements. The key thing is that I usually add the handlers I want to the root logger, using levels and sometimes logging.Filters to get the events I want to the appropriate files, console, syslogs etc. You can of course add handlers to any other loggers too, but there isn't commonly a need for this in my experience.

In each module, I define a logger using

<pre><code>logger = logging.getLogger(__name__)
</code></pre>

and use that for logging events in the module (and, if I want to differentiate further) use a logger which is a child of the logger created above.

If my app is going to be potentially used in a site which doesn't configure logging in settings.py, I define a NullHandler somewhere as follows:

<pre><code>#someutils.py

class NullHandler(logging.Handler):
 def emit(self, record):
 pass

null_handler = NullHandler()
</code></pre>

and ensure that an instance of it is added to all loggers created in the modules in my apps which use logging. (Note: NullHandler is already in the logging package for Python 3.1, and will be in Python 2.7.) So:

<pre><code>logger = logging.getLogger(__name__)
logger.addHandler(someutils.null_handler)
</code></pre>

This is done to ensure that your modules play nicely in a site which doesn't configure logging in settings.py, and that you don't get any annoying "No handlers could be found for logger X.Y.Z" messages (which are warnings about potentially misconfigured logging).

Doing it this way meets your stated requirements:

<ul>
<li>You can set up different log handlers for different events, as you currently do.</li>
<li>Easy access to loggers in your modules - use <code>getLogger(__name__)</code>.</li>
<li>Easily applicable to command-line modules - they also import <code>settings.py</code>.</li>
</ul>

Update: Note that as of version 1.3, Django now incorporates <a href="https://docs.djangoproject.com/en/dev/topics/logging/" rel="noreferrer">support for logging</a>.

blocks|key|3296506|text|我们使用logging.ini文件在顶级urls.py中初始化日志记录。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|3296507|settings.py中提供了logging.ini的位置，但仅此而已。|3296508|然后，每个模块执行以下操作|3296509|logger+=+logging.getLogger(__name__)|code-block|syntax|javascript|3296510|为了区分测试、开发和生产实例，我们有不同的logging.ini文件。在大多数情况下，我们有一个“控制台日志”，它只在stderr中出现错误。我们有一个“应用程序日志”，它使用到日志目录的常规滚动日志文件。|3296511|entityMap^0|4|B|K|7|0|0|B|F|B|0|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@$9|T|A|U|B|C]|$9|V|A|W|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|X|8|@$9|Y|A|Z|B|C]|$9|10|A|11|B|C]]|D|@]|E|$]]|$1|H|3|I|5|6|7|12|8|@]|D|@]|E|$]]|$1|J|3|K|5|L|7|13|8|@]|D|@]|E|$M|N]]|$1|O|3|P|5|6|7|14|8|@]|D|@]|E|$]]|$1|Q|3|-4|5|6|7|15|8|@]|D|@]|E|$]]]|R|$]]

We initialize logging in the top-level <code>urls.py</code> by using a <code>logging.ini</code> file.

The location of the <code>logging.ini</code> is provided in <code>settings.py</code>, but that's all.

Each module then does

<pre><code>logger = logging.getLogger(__name__)
</code></pre>

To distinguish testing, development and production instances, we have different logging.ini files. For the most part, we have a "console log" that goes to stderr with Errors only. We have an "application log" that uses a regular rolling log file that goes to a logs directory.

blocks|key|327141|text|我知道这是一个已经解决的问题，但是根据django+>=+1.3，有一个新的日志设置。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|327142|从旧到新并不是自动的，所以我想我应该把它写下来。|327143|当然，还可以查看the+django+doc获取更多信息。|offset|length|327144|这是使用django-admin+createproject+v1.3默认创建的基本conf+-+mileage可能会随着最新的django版本而变化：|327145|LOGGING+=+{
++++'version':+1,
++++'disable_existing_loggers':+False,
++++'handlers':+{
++++++++'mail_admins':+{
++++++++++++'level':+'ERROR',
++++++++++++'class':+'django.utils.log.AdminEmailHandler',
++++++++}
++++},
++++'loggers':+{
++++++++'django.request':+{
++++++++++++'handlers':+['mail_admins'],
++++++++++++'level':+'ERROR',
++++++++++++'propagate':+True,
++++++++}
++++}
}|code-block|syntax|javascript|327146|此结构基于标准Python+logging+dictConfig，它规定了以下块：|327147|327148|formatters+-对应的值将是一个字典，其中每个键是一个格式器id，每个值是一个描述如何配置相应的格式器的字典。-对应值将是一个字典，其中每个键是一个过滤器id，每个值是一个描述如何配置相应的过滤器的字典。-对应值将是一个字典，其中每个键是一个处理器id，每个值是一个描述如何配置相应的处理器实例的字典。每个处理程序都有以下键：|unordered-list-item|style|CODE|327149|327150|-+`class`+(mandatory).+This+is+the+fully+qualified+name+of+the+handler+class.
-+`level`+(optional).+The+level+of+the+handler.
-+`formatter`+(optional).+The+id+of+the+formatter+for+this+handler.
-+`filters`+(optional).+A+list+of+ids+of+the+filters+for+this+handler.|327151|​|327152|我通常至少这样做：|327153|327154|add+a+.log+a.log+to+write+to+this+log|327155|+(为我的应用程序添加要写入此日志的日志)|327156|这将转换为：|327157|LOGGING+=+{
++++'version':+1,
++++'disable_existing_loggers':+False,
++++'formatters':+{
++++++++'verbose':+{
++++++++++++'format':+'%25(levelname)s+%25(asctime)s+%25(module)s+%25(process)d+%25(thread)d+%25(message)s'
++++++++},
++++++++'simple':+{
++++++++++++'format':+'%25(levelname)s+%25(message)s'
++++++++},
++++},
++++'filters':+{
++++++++'require_debug_false':+{
++++++++++++'()':+'django.utils.log.RequireDebugFalse'
++++++++}
++++},
++++'handlers':+{
++++++++'null':+{
++++++++++++'level':'DEBUG',
++++++++++++'class':'django.utils.log.NullHandler',
++++++++},
++++++++'console':{
++++++++++++'level':+'DEBUG',
++++++++++++'class':+'logging.StreamHandler',
++++++++++++'formatter':+'simple'
++++++++},
++++++++#+I+always+add+this+handler+to+facilitate+separating+loggings
++++++++'log_file':{
++++++++++++'level':+'DEBUG',
++++++++++++'class':+'logging.handlers.RotatingFileHandler',
++++++++++++'filename':+os.path.join(VAR_ROOT,+'logs/django.log'),
++++++++++++'maxBytes':+'16777216',+#+16megabytes
++++++++++++'formatter':+'verbose'
++++++++},
++++++++'mail_admins':+{
++++++++++++'level':+'ERROR',
++++++++++++'filters':+['require_debug_false'],
++++++++++++'class':+'django.utils.log.AdminEmailHandler',
++++++++++++'include_html':+True,
++++++++}
++++},
++++'loggers':+{
++++++++'django.request':+{
++++++++++++'handlers':+['mail_admins'],
++++++++++++'level':+'ERROR',
++++++++++++'propagate':+True,
++++++++},
++++++++'apps':+{+#+I+keep+all+my+of+apps+under+'apps'+folder,+but+you+can+also+add+them+one+by+one,+and+this+depends+on+how+your+virtualenv/paths+are+set
++++++++++++'handlers':+['log_file'],
++++++++++++'level':+'INFO',
++++++++++++'propagate':+True,
++++++++},
++++},
++++#+you+can+also+shortcut+'loggers'+and+just+configure+logging+for+EVERYTHING+at+once
++++'root':+{
++++++++'handlers':+['console',+'mail_admins'],
++++++++'level':+'INFO'
++++},
}|327158|编辑|BOLD|327159|请参阅request+exceptions+are+now+always+logged和Ticket+#16288：|327160|我更新了上面的示例配置文件，显式地包含了正确的mail_admins过滤器，以便在默认情况下，当debug为True时不会发送电子邮件。|327161|您应该添加一个过滤器：|327162|'filters':+{
++++'require_debug_false':+{
++++++++'()':+'django.utils.log.RequireDebugFalse'
++++}
},|327163|并将其应用于mail_admins处理程序：|327164|++++'mail_admins':+{
++++++++'level':+'ERROR',
++++++++'filters':+['require_debug_false'],
++++++++'class':+'django.utils.log.AdminEmailHandler',
++++++++'include_html':+True,
++++}|327165|否则，如果settings.DEBUG为True，则django.core.handers.base.handle_uncaught_exception不会将错误传递给'django.request‘记录器。|327166|如果你在Django+1.5中不这样做，你会得到一个|327167|327168|+DeprecationWarning：'mail_admins‘日志记录处理程序上没有定义筛选器:正在添加隐式debug-false-only筛选器|blockquote|327169|327170|327171|但在django+1.4和django+1.5中仍然可以正常工作。|327172|**结束编辑**|327173|该conf的灵感来自于django文档中的示例conf，但添加了日志文件部分。|327174|我还经常做以下事情：|327175|LOG_LEVEL+=+'DEBUG'+if+DEBUG+else+'INFO'

...
++++'level':+LOG_LEVEL
...|327176|然后，在我的python代码中，我总是添加一个NullHandler，以防没有定义任何日志配置文件。这避免了没有指定处理程序的警告。对于不一定只在Django+(ref)中调用的库，尤其有用。|327177|import+logging
#+Get+an+instance+of+a+logger
logger+=+logging.getLogger(__name__)
class+NullHandler(logging.Handler):+#exists+in+python+3.1
++++def+emit(self,+record):
++++++++pass
nullhandler+=+logger.addHandler(NullHandler())

#+here+you+can+also+add+some+local+logger+should+you+want:+to+stdout+with+streamhandler,+or+to+a+local+file...|327178|..。|327179|logger.warning('etc.etc.')|327180|希望这能有所帮助！|327181|entityMap|0|LINK|mutability|MUTABLE|url|http://docs.djangoproject.com/en/dev/topics/logging|1|http://docs.python.org/library/logging.config.html#configuration-dictionary-schema|2|https://docs.djangoproject.com/en/dev/releases/1.4/#request-exceptions-are-now-always-logged|3|https://code.djangoproject.com/ticket/16288|4|http://docs.python.org/howto/logging.html#configuring-logging-for-a-library^0|0|0|8|E|0|0|0|0|7|P|1|0|0|0|A|0|0|0|0|0|0|0|0|0|0|0|2|0|3|14|2|18|D|3|0|0|0|0|0|0|Q|1E|0|0|0|0|0|0|0|0|0|0|0|29|3|4|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|31|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|32|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|33|8|@]|9|@$F|34|G|35|1|36]]|A|$]]|$1|H|3|I|5|6|7|37|8|@]|9|@]|A|$]]|$1|J|3|K|5|L|7|38|8|@]|9|@]|A|$M|N]]|$1|O|3|P|5|6|7|39|8|@]|9|@$F|3A|G|3B|1|3C]]|A|$]]|$1|Q|3|-4|5|6|7|3D|8|@]|9|@]|A|$]]|$1|R|3|S|5|T|7|3E|8|@$F|3F|G|3G|U|V]]|9|@]|A|$]]|$1|W|3|-4|5|6|7|3H|8|@]|9|@]|A|$]]|$1|X|3|Y|5|L|7|3I|8|@]|9|@]|A|$M|N]]|$1|Z|3|10|5|6|7|3J|8|@]|9|@]|A|$]]|$1|11|3|12|5|6|7|3K|8|@]|9|@]|A|$]]|$1|13|3|-4|5|6|7|3L|8|@]|9|@]|A|$]]|$1|14|3|15|5|T|7|3M|8|@]|9|@]|A|$]]|$1|16|3|17|5|6|7|3N|8|@]|9|@]|A|$]]|$1|18|3|19|5|6|7|3O|8|@]|9|@]|A|$]]|$1|1A|3|1B|5|L|7|3P|8|@]|9|@]|A|$M|N]]|$1|1C|3|1D|5|6|7|3Q|8|@$F|3R|G|3S|U|1E]]|9|@]|A|$]]|$1|1F|3|1G|5|6|7|3T|8|@]|9|@$F|3U|G|3V|1|3W]|$F|3X|G|3Y|1|3Z]]|A|$]]|$1|1H|3|1I|5|6|7|40|8|@]|9|@]|A|$]]|$1|1J|3|1K|5|6|7|41|8|@]|9|@]|A|$]]|$1|1L|3|1M|5|L|7|42|8|@]|9|@]|A|$M|N]]|$1|1N|3|1O|5|6|7|43|8|@]|9|@]|A|$]]|$1|1P|3|1Q|5|L|7|44|8|@]|9|@]|A|$M|N]]|$1|1R|3|1S|5|6|7|45|8|@$F|46|G|47|U|V]]|9|@]|A|$]]|$1|1T|3|1U|5|6|7|48|8|@]|9|@]|A|$]]|$1|1V|3|-4|5|6|7|49|8|@]|9|@]|A|$]]|$1|1W|3|1X|5|1Y|7|4A|8|@]|9|@]|A|$]]|$1|1Z|3|-4|5|6|7|4B|8|@]|9|@]|A|$]]|$1|20|3|-4|5|6|7|4C|8|@]|9|@]|A|$]]|$1|21|3|22|5|6|7|4D|8|@]|9|@]|A|$]]|$1|23|3|24|5|6|7|4E|8|@]|9|@]|A|$]]|$1|25|3|26|5|6|7|4F|8|@]|9|@]|A|$]]|$1|27|3|28|5|6|7|4G|8|@]|9|@]|A|$]]|$1|29|3|2A|5|L|7|4H|8|@]|9|@]|A|$M|N]]|$1|2B|3|2C|5|6|7|4I|8|@]|9|@$F|4J|G|4K|1|4L]]|A|$]]|$1|2D|3|2E|5|L|7|4M|8|@]|9|@]|A|$M|N]]|$1|2F|3|2G|5|6|7|4N|8|@]|9|@]|A|$]]|$1|2H|3|2I|5|L|7|4O|8|@]|9|@]|A|$M|N]]|$1|2J|3|2K|5|6|7|4P|8|@]|9|@]|A|$]]|$1|2L|3|-4|5|6|7|4Q|8|@]|9|@]|A|$]]]|2M|$2N|$5|2O|2P|2Q|A|$2R|2S]]|2T|$5|2O|2P|2Q|A|$2R|2U]]|2V|$5|2O|2P|2Q|A|$2R|2W]]|2X|$5|2O|2P|2Q|A|$2R|2Y]]|2Z|$5|2O|2P|2Q|A|$2R|30]]]]

I know this is a solved answer already, but as per django >= 1.3 there's a new logging setting.

Moving from old to new is not automatic, so I thought i'll write it down here.

And of course checkout <a href="http://docs.djangoproject.com/en/dev/topics/logging" rel="noreferrer" title="Django Logging Doc">the django doc</a> for some more.

This is the basic conf, created by default with django-admin createproject v1.3 - mileage might change with latest django versions:

<pre><code>LOGGING = {
 'version': 1,
 'disable_existing_loggers': False,
 'handlers': {
 'mail_admins': {
 'level': 'ERROR',
 'class': 'django.utils.log.AdminEmailHandler',
 }
 },
 'loggers': {
 'django.request': {
 'handlers': ['mail_admins'],
 'level': 'ERROR',
 'propagate': True,
 }
 }
}
</code></pre>

This structure is based upon the standard <a href="http://docs.python.org/library/logging.config.html#configuration-dictionary-schema" rel="noreferrer" title="Python Logging Configuration Doc">Python logging dictConfig</a>, that dictates the following blocks:

<ul>
<li><code>formatters</code> - the corresponding value will be a dict in which each key is a formatter id and each value is a dict describing how to configure the corresponding Formatter instance.</li>
<li><code>filters</code> - the corresponding value will be a dict in which each key is a filter id and each value is a dict describing how to configure the corresponding Filter instance.</li>
<li><code>handlers</code> - the corresponding value will be a dict in which each key is a handler id and each value is a dict describing how to configure the corresponding Handler instance. Each handler has the following keys:

<ul>
<li><code>class</code> (mandatory). This is the fully qualified name of the handler class.</li>
<li><code>level</code> (optional). The level of the handler.</li>
<li><code>formatter</code> (optional). The id of the formatter for this handler.</li>
<li><code>filters</code> (optional). A list of ids of the filters for this handler.</li>
</ul></li>
</ul>

I usually do at least this:

<ul>
<li>add a .log file</li>
<li>configure my apps to write to this log</li>
</ul>

Which translates into:

<pre><code>LOGGING = {
 'version': 1,
 'disable_existing_loggers': False,
 'formatters': {
 'verbose': {
 'format': '%(levelname)s %(asctime)s %(module)s %(process)d %(thread)d %(message)s'
 },
 'simple': {
 'format': '%(levelname)s %(message)s'
 },
 },
 'filters': {
 'require_debug_false': {
 '()': 'django.utils.log.RequireDebugFalse'
 }
 },
 'handlers': {
 'null': {
 'level':'DEBUG',
 'class':'django.utils.log.NullHandler',
 },
 'console':{
 'level': 'DEBUG',
 'class': 'logging.StreamHandler',
 'formatter': 'simple'
 },
 # I always add this handler to facilitate separating loggings
 'log_file':{
 'level': 'DEBUG',
 'class': 'logging.handlers.RotatingFileHandler',
 'filename': os.path.join(VAR_ROOT, 'logs/django.log'),
 'maxBytes': '16777216', # 16megabytes
 'formatter': 'verbose'
 },
 'mail_admins': {
 'level': 'ERROR',
 'filters': ['require_debug_false'],
 'class': 'django.utils.log.AdminEmailHandler',
 'include_html': True,
 }
 },
 'loggers': {
 'django.request': {
 'handlers': ['mail_admins'],
 'level': 'ERROR',
 'propagate': True,
 },
 'apps': { # I keep all my of apps under 'apps' folder, but you can also add them one by one, and this depends on how your virtualenv/paths are set
 'handlers': ['log_file'],
 'level': 'INFO',
 'propagate': True,
 },
 },
 # you can also shortcut 'loggers' and just configure logging for EVERYTHING at once
 'root': {
 'handlers': ['console', 'mail_admins'],
 'level': 'INFO'
 },
}
</code></pre>

edit

See <a href="https://docs.djangoproject.com/en/dev/releases/1.4/#request-exceptions-are-now-always-logged" rel="noreferrer">request exceptions are now always logged</a> and <a href="https://code.djangoproject.com/ticket/16288" rel="noreferrer">Ticket #16288</a>: 

I updated the above sample conf to explicitly include the correct filter for mail_admins so that, by default, emails are not sent when debug is True.

You should add a filter:

<pre><code>'filters': {
 'require_debug_false': {
 '()': 'django.utils.log.RequireDebugFalse'
 }
},
</code></pre>

and apply it to the mail_admins handler:

<pre><code> 'mail_admins': {
 'level': 'ERROR',
 'filters': ['require_debug_false'],
 'class': 'django.utils.log.AdminEmailHandler',
 'include_html': True,
 }
</code></pre>

Otherwise the <code>django.core.handers.base.handle_uncaught_exception</code> doesn't pass errors to the 'django.request' logger if settings.DEBUG is True.

If you don't do this in Django 1.5 you'll get a 

<blockquote>
 DeprecationWarning: You have no filters defined on the 'mail_admins' logging handler: adding implicit debug-false-only filter
</blockquote>

but things will still work correctly BOTH in django 1.4 and django 1.5.

** end edit **

That conf is strongly inspired by the sample conf in the django doc, but adding the log file part.

I often also do the following:

<pre><code>LOG_LEVEL = 'DEBUG' if DEBUG else 'INFO'

...
 'level': LOG_LEVEL
...
</code></pre>

Then in my python code I always add a NullHandler in case no logging conf is defined whatsoever. This avoid warnings for no Handler specified. Especially useful for libs that are not necessarily called only in Django (<a href="http://docs.python.org/howto/logging.html#configuring-logging-for-a-library" rel="noreferrer" title="Python logging for a library">ref</a>)

<pre><code>import logging
# Get an instance of a logger
logger = logging.getLogger(__name__)
class NullHandler(logging.Handler): #exists in python 3.1
 def emit(self, record):
 pass
nullhandler = logger.addHandler(NullHandler())

# here you can also add some local logger should you want: to stdout with streamhandler, or to a local file...
</code></pre>

[...]

<pre><code>logger.warning('etc.etc.')
</code></pre>

Hope this helps!

I have yet to find a way of setting up Python logging with Django that I'm happy with. My requirements are fairly simple:

<ul>
<li>Different log handlers for different events - that is, I want to be able to log to different files</li>
<li>Easy access to loggers in my modules. The module should be able to find its logger with little effort.</li>
<li>Should be easily applicable to command-line modules. Parts of the system are stand-alone command line or daemon processes. Logging should be easily usable with these modules.</li>
</ul>

My current setup is to use a <code>logging.conf</code> file and setup logging in each module I log from. It doesn't feel right. 

Do you have a logging setup that you like? Please detail it: how do you setup the configuration (do you use <code>logging.conf</code> or set it up in code), where/when do you initiate the loggers, and how do you get access to them in your modules, etc.

Elegant setup of Python logging in Django

日志文件

Django

Python

我还没有找到一种使用Django设置Python日志的方法，我对此很满意。我的需求相当简单：不同的日志处理程序为不同的事件-也就是说，我希望能够记录到不同的文件轻松访问我的模块中的记录器。该模块应该能够轻松地找到它的记录器。应该很容易地适用于命令行模块。系统的一部分是独立的命令行进程或守护进程。日志记录应该很容易与这些...

问Django中Python日志的优雅设置
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Django中Python日志的优雅设置EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Django中Python日志的优雅设置
EN