StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
1018696
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2009-06-19T15:47:03.447
FavoriteCount
0
LastActivityDate
2009-06-19T15:47:03.447
LastEditDate
LastEditorUserId
0
OwnerUserId
41747
ParentId
1018527
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
Interesting... I played a little in the console and it looks like the second call to <code>logging.config.fileConfig</code> is mucking things up. Not sure why this is though... Here's a transcript that shows the problem: <pre><code>lorien$ python2.5 Python 2.5.1 (r251:54863, Feb 6 2009, 19:02:12) [GCC 4.0.1 (Apple Inc. build 5465)] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> import logging >>> import logging.config >>> logging.config.fileConfig('logger.conf') >>> alog = logging.getLogger('a.submod') >>> alog.info('foo') foo >>> import logging >>> import logging.config >>> alog.info('foo') foo >>> logging.config.fileConfig('logger.conf') >>> alog.info('foo') >>> alog = logging.getLogger('a.submod') >>> alog.info('foo') >>> >>> blog = logging.getLogger('b.submod') >>> blog.info('foo') foo >>> </code></pre> As soon as I call <code>logging.config.fileConfig</code> the second time, my logger instance stops logging. Grabbing a new logging instance doesn't help since it's the same object. If I wait until after configuring both times to fetch the logger instances, then things work - this is why the <code>blog</code> instance works. My suggestion is to delay grabbing the logger instances until you are in the functions. If you move the calls to <code>logging.getLogger()</code> into <code>function_one</code> and <code>function_two</code>, then everything works well.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POPython logging incompatibilty between 2.5 and 2.6
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USD.Shawley
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. This table or related slice is empty.
VotesPostIdCreationDate
1. This table or related slice is empty.
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.