StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POPython logging for non-trivial uses?
primarykey
Id
1580828
data
AcceptedAnswerId
1580929
AnswerCount
2
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2009-10-16T23:04:28.770
FavoriteCount
2
LastActivityDate
2010-08-05T05:24:40.873
LastEditDate
2009-10-17T00:26:50.997
LastEditorUserId
0
OwnerUserId
0
ParentId
0
PostTypeId
1
Score
1
ViewCount
1259
LastEditorDisplayName
user191505
text
Body
I'm attempting to use the python logging module to do complex things. I'll leave the motivation for this design out because it would greatly lengthen the post, but I need to have a root logger that spams a regular log file for our code and libraries that use logging -- and a collection of other loggers that go to different log files. The overall setup should look like this. I will do everything to stdout in this example to simplify the code. <pre><code> import logging, sys root = logging.getLogger('') top = logging.getLogger('top') bottom = logging.getLogger('top.bottom') class KillFilter(object): def filter(self, msg): return 0 root_handler = logging.StreamHandler(sys.stdout) top_handler = logging.StreamHandler(sys.stdout) bottom_handler = logging.StreamHandler(sys.stdout) root_handler.setFormatter(logging.Formatter('ROOT')) top_handler.setFormatter(logging.Formatter('TOP HANDLER')) bottom_handler.setFormatter(logging.Formatter("BOTTOM HANDLER")) msg_killer = KillFilter() root.addHandler(root_handler) top.addHandler(top_handler) bottom.addHandler(bottom_handler) top.addFilter(msg_killer) root.error('hi') top.error('hi') bottom.error('hi') </code></pre> This outputs <pre><code> ROOT BOTTOM HANDLER ROOT </pre></code> The second root handler call should not because according to logging documentation the <code>msg_killer</code> will stop the message from going up to the root logger. Obviously the documentation could use improvement. Edit: removed my "in the moment" harsh words for python logging.
Tags
<python><logging>
Title
Python logging for non-trivial uses?
singulars
PostAcceptedAnswerId
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. This table or related slice is empty.
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
2. PO
 singulars
 PostTypePostTypeId
 PTAnswer
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 POPython logging for non-trivial uses?
 UserUserId
 USennuikiller
 VoteTypeVoteTypeId
 VTFavorite
2. VO
 singulars
 PostPostId
 POPython logging for non-trivial uses?
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
3. VO
 singulars
 PostPostId
 POPython logging for non-trivial uses?
 UserUserId
 USapose
 VoteTypeVoteTypeId
 VTFavorite
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.