blocks|key|838271|text|在mod_wsgi下运行时，打印到stderr的文本将显示在httpd的错误日志中。您可以直接使用print，也可以改用logging。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|838272|print+>>sys.stderr,+'Goodbye,+cruel+world!'|code-block|syntax|javascript|838273|entityMap^0|1D|5|1O|7|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@$9|N|A|O|B|C]|$9|P|A|Q|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|R|8|@]|D|@]|E|$I|J]]|$1|K|3|-4|5|6|7|S|8|@]|D|@]|E|$]]]|L|$]]

Text printed to stderr will show up in httpd's error log when running under mod_wsgi. You can either use <code>print</code> directly, or use <code>logging</code> instead.

<pre><code>print &gt;&gt;sys.stderr, 'Goodbye, cruel world!'
</code></pre>

blocks|key|1053029|text|您可以在settings.py文件中配置日志记录。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1053030|举个例子：|1053031|if+DEBUG:
++++#+will+output+to+your+console
++++logging.basicConfig(
++++++++level+=+logging.DEBUG,
++++++++format+=+'%25(asctime)s+%25(levelname)s+%25(message)s',
++++)
else:
++++#+will+output+to+logging+file
++++logging.basicConfig(
++++++++level+=+logging.DEBUG,
++++++++format+=+'%25(asctime)s+%25(levelname)s+%25(message)s',
++++++++filename+=+'/my_log_file.log',
++++++++filemode+=+'a'
++++)|code-block|syntax|javascript|1053032|然而，这取决于DEBUG的设置，也许你不想担心它是如何设置的。请在How+can+I+tell+whether+my+Django+application+is+running+on+development+server+or+not?上查看此答案，以获得编写该条件的更好方法。编辑:上面的例子来自Django+1.1项目，Django中的日志配置自该版本以来有所改变。|1053033|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/questions/1291755/how-can-i-tell-whether-my-django-application-is-running-on-development-server-or/1291858#1291858^0|4|B|0|0|0|X|2D|0|0^^$0|@$1|2|3|4|5|6|7|W|8|@$9|X|A|Y|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|Z|8|@]|D|@]|E|$]]|$1|H|3|I|5|J|7|10|8|@]|D|@]|E|$K|L]]|$1|M|3|N|5|6|7|11|8|@]|D|@$9|12|A|13|1|14]]|E|$]]|$1|O|3|-4|5|6|7|15|8|@]|D|@]|E|$]]]|P|$Q|$5|R|S|T|E|$U|V]]]]

You can configure logging in your <code>settings.py</code> file. 

One example:

<pre><code>if DEBUG:
 # will output to your console
 logging.basicConfig(
 level = logging.DEBUG,
 format = '%(asctime)s %(levelname)s %(message)s',
 )
else:
 # will output to logging file
 logging.basicConfig(
 level = logging.DEBUG,
 format = '%(asctime)s %(levelname)s %(message)s',
 filename = '/my_log_file.log',
 filemode = 'a'
 )
</code></pre>

However that's dependent upon setting DEBUG, and maybe you don't want to have to worry about how it's set up. See this answer on <a href="https://stackoverflow.com/questions/1291755/how-can-i-tell-whether-my-django-application-is-running-on-development-server-or/1291858#1291858">How can I tell whether my Django application is running on development server or not?</a> for a better way of writing that conditional. Edit: the example above is from a Django 1.1 project, logging configuration in Django has changed somewhat since that version.

blocks|key|1053067|text|使用tagalog+(https://github.com/dorkitude/tagalog)可以很容易地做到这一点|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1053068|例如，当标准python模块写入以追加模式打开的文件对象时，App+Engine模块(https://github.com/dorkitude/tagalog/blob/master/tagalog_appengine.py)会覆盖此行为，转而使用logging.INFO。|1053069|要在App+Engine项目中获得此行为，可以简单地执行以下操作：|1053070|import+tagalog.tagalog_appengine+as+tagalog
tagalog.log('whatever+message',+['whatever','tags'])|code-block|syntax|javascript|1053071|您可以轻松地自己扩展模块并覆盖日志函数。|1053072|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/dorkitude/tagalog|1|https://github.com/dorkitude/tagalog/blob/master/tagalog/_appengine.py^0|2|7|B|10|0|0|3G|C|17|1X|1|0|0|0|0^^$0|@$1|2|3|4|5|6|7|10|8|@$9|11|A|12|B|C]]|D|@$9|13|A|14|1|15]]|E|$]]|$1|F|3|G|5|6|7|16|8|@$9|17|A|18|B|C]]|D|@$9|19|A|1A|1|1B]]|E|$]]|$1|H|3|I|5|6|7|1C|8|@]|D|@]|E|$]]|$1|J|3|K|5|L|7|1D|8|@]|D|@]|E|$M|N]]|$1|O|3|P|5|6|7|1E|8|@]|D|@]|E|$]]|$1|Q|3|-4|5|6|7|1F|8|@]|D|@]|E|$]]]|R|$S|$5|T|U|V|E|$W|X]]|Y|$5|T|U|V|E|$W|Z]]]]

You can do this pretty easily with <code>tagalog</code> (https://github.com/dorkitude/tagalog)

For instance, while the standard python module writes to a file object opened in append mode, the App Engine module (https://github.com/dorkitude/tagalog/blob/master/tagalog_appengine.py) overrides this behavior and instead uses <code>logging.INFO</code>.

To get this behavior in an App Engine project, one could simply do:

<pre><code>import tagalog.tagalog_appengine as tagalog
tagalog.log('whatever message', ['whatever','tags'])
</code></pre>

You could extend the module yourself and overwrite the log function without much difficulty.

blocks|key|838394|text|这是一个基于Django日志的解决方案。它使用调试设置，而不是实际检查您是否正在运行开发服务器，但是如果您找到更好的方法来检查它，那么它应该很容易适应。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|838395|LOGGING+=+{
++++'version':+1,
++++'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'
++++++++},
++++},
++++'handlers':+{
++++++++'console':+{
++++++++++++'level':+'DEBUG',
++++++++++++'class':+'logging.StreamHandler',
++++++++++++'formatter':+'simple'
++++++++},
++++++++'file':+{
++++++++++++'level':+'DEBUG',
++++++++++++'class':+'logging.FileHandler',
++++++++++++'filename':+'/path/to/your/file.log',
++++++++++++'formatter':+'simple'
++++++++},
++++},
++++'loggers':+{
++++++++'django':+{
++++++++++++'handlers':+['file'],
++++++++++++'level':+'DEBUG',
++++++++++++'propagate':+True,
++++++++},
++++}
}

if+DEBUG:
++++#+make+all+loggers+use+the+console.
++++for+logger+in+LOGGING['loggers']:
++++++++LOGGING['loggers'][logger]['handlers']+=+['console']|code-block|syntax|javascript|838396|详情请参见https://docs.djangoproject.com/en/dev/topics/logging/。|offset|length|838397|entityMap|0|LINK|mutability|MUTABLE|url|https://docs.djangoproject.com/en/dev/topics/logging/^0|0|0|5|1H|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|T|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|U|8|@]|9|@$I|V|J|W|1|X]]|A|$]]|$1|K|3|-4|5|6|7|Y|8|@]|9|@]|A|$]]]|L|$M|$5|N|O|P|A|$Q|R]]]]

Here's a Django logging-based solution. It uses the DEBUG setting rather than actually checking whether or not you're running the development server, but if you find a better way to check for that it should be easy to adapt.

<pre><code>LOGGING = {
 'version': 1,
 'formatters': {
 'verbose': {
 'format': '%(levelname)s %(asctime)s %(module)s %(process)d %(thread)d %(message)s'
 },
 'simple': {
 'format': '%(levelname)s %(message)s'
 },
 },
 'handlers': {
 'console': {
 'level': 'DEBUG',
 'class': 'logging.StreamHandler',
 'formatter': 'simple'
 },
 'file': {
 'level': 'DEBUG',
 'class': 'logging.FileHandler',
 'filename': '/path/to/your/file.log',
 'formatter': 'simple'
 },
 },
 'loggers': {
 'django': {
 'handlers': ['file'],
 'level': 'DEBUG',
 'propagate': True,
 },
 }
}

if DEBUG:
 # make all loggers use the console.
 for logger in LOGGING['loggers']:
 LOGGING['loggers'][logger]['handlers'] = ['console']
</code></pre>

see <a href="https://docs.djangoproject.com/en/dev/topics/logging/" rel="noreferrer">https://docs.djangoproject.com/en/dev/topics/logging/</a> for details.

blocks|key|838425|text|我使用的是：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|838426|logging.conf：|838427|[loggers]
keys=root,applog
[handlers]
keys=rotateFileHandler,rotateConsoleHandler

[formatters]
keys=applog_format,console_format

[formatter_applog_format]
format=%25(asctime)s-[%25(levelname)-8s]:%25(message)s

[formatter_console_format]
format=%25(asctime)s-%25(filename)s%25(lineno)d[%25(levelname)s]:%25(message)s

[logger_root]
level=DEBUG
handlers=rotateFileHandler,rotateConsoleHandler

[logger_applog]
level=DEBUG
handlers=rotateFileHandler
qualname=simple_example

[handler_rotateFileHandler]
class=handlers.RotatingFileHandler
level=DEBUG
formatter=applog_format
args=('applog.log',+'a',+10000,+9)

[handler_rotateConsoleHandler]
class=StreamHandler
level=DEBUG
formatter=console_format
args=(sys.stdout,)|code-block|syntax|javascript|838428|testapp.py：|838429|import+logging
import+logging.config

def+main():
++++logging.config.fileConfig('logging.conf')
++++logger+=+logging.getLogger('applog')

++++logger.debug('debug+message')
++++logger.info('info+message')
++++logger.warn('warn+message')
++++logger.error('error+message')
++++logger.critical('critical+message')
++++#logging.shutdown()

if+__name__+==+'__main__':
++++main()|838430|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|P|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|Q|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|R|8|@]|9|@]|A|$]]|$1|K|3|L|5|F|7|S|8|@]|9|@]|A|$G|H]]|$1|M|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|N|$]]

I use this:

logging.conf:

<pre><code>[loggers]
keys=root,applog
[handlers]
keys=rotateFileHandler,rotateConsoleHandler

[formatters]
keys=applog_format,console_format

[formatter_applog_format]
format=%(asctime)s-[%(levelname)-8s]:%(message)s

[formatter_console_format]
format=%(asctime)s-%(filename)s%(lineno)d[%(levelname)s]:%(message)s

[logger_root]
level=DEBUG
handlers=rotateFileHandler,rotateConsoleHandler

[logger_applog]
level=DEBUG
handlers=rotateFileHandler
qualname=simple_example

[handler_rotateFileHandler]
class=handlers.RotatingFileHandler
level=DEBUG
formatter=applog_format
args=('applog.log', 'a', 10000, 9)

[handler_rotateConsoleHandler]
class=StreamHandler
level=DEBUG
formatter=console_format
args=(sys.stdout,)
</code></pre>

testapp.py:

<pre><code>import logging
import logging.config

def main():
 logging.config.fileConfig('logging.conf')
 logger = logging.getLogger('applog')

 logger.debug('debug message')
 logger.info('info message')
 logger.warn('warn message')
 logger.error('error message')
 logger.critical('critical message')
 #logging.shutdown()

if __name__ == '__main__':
 main()
</code></pre>

blocks|key|1053134|text|这在我的local.py中工作得很好，省去了我搞砸常规日志的麻烦：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1053135|from+.settings+import+*

LOGGING['handlers']['console']+=+{
++++'level':+'DEBUG',
++++'class':+'logging.StreamHandler',
++++'formatter':+'verbose'
}
LOGGING['loggers']['foo.bar']+=+{
++++'handlers':+['console'],
++++'propagate':+False,
++++'level':+'DEBUG',
}|code-block|syntax|javascript|1053136|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

This works quite well in my local.py, saves me messing up the regular logging:

<pre><code>from .settings import *

LOGGING['handlers']['console'] = {
 'level': 'DEBUG',
 'class': 'logging.StreamHandler',
 'formatter': 'verbose'
}
LOGGING['loggers']['foo.bar'] = {
 'handlers': ['console'],
 'propagate': False,
 'level': 'DEBUG',
}
</code></pre>

How can I send trace messages to the console (like <code>print</code>) when I'm running my Django app under <code>manage.py runserver</code>, but have those messages sent to a log file when I'm running the app under Apache?

I reviewed <a href="http://docs.djangoproject.com/en/dev/topics/logging/" rel="noreferrer">Django logging</a> and although I was impressed with its flexibility and configurability for advanced uses, I'm still stumped with how to handle my simple use-case.

Python/Django: log to console under runserver, log to file under Apache

日志文件

服务器

Django

当我在manage.py runserver下运行我的Django应用程序时，我如何将跟踪消息发送到控制台(如print)，但当我在Apache下运行该应用程序时，如何将这些消息发送到日志文件？我回顾了，尽管它的灵活性和高级用途的可配置性给我留下了深刻的印象，但我仍然对如何处理我的简单用例感到困惑。

问Python/Django:日志到runserver下的控制台，日志到Apache下的文件
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Python/Django:日志到runserver下的控制台，日志到Apache下的文件EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Python/Django:日志到runserver下的控制台，日志到Apache下的文件
EN