StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
17488467
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-07-05T12:02:35.700
FavoriteCount
0
LastActivityDate
2013-07-05T12:02:35.700
LastEditDate
LastEditorUserId
0
OwnerUserId
0
ParentId
17471078
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
You were on the right track. When parsing the code tree, it just runs through <code>PyEval_FrameEx</code> multiple times. In the end, it will call <code>format_exc_check_arg()</code> to format the error, which for me happens at line 2100 in the <code>ceval.c</code> of the Python version 3.3.2 source. <code>format_exc_check_arg()</code> deduces the offensive 'object' (<code>prnt</code>) and calls <code>PyErr_Format</code> in <code>errors.c</code> to properly format the exception string (the exception type and its corresponding string, <code>NAME_ERROR_MSG</code>, were already passed to <code>format_exc_check_arg()</code> from this line 2100. I used simply this code for testing: <pre><code>prnt('Line1') </code></pre> and then run it through a <a href="http://docs.python.org/devguide/setup.html#compiling-for-debugging" rel="nofollow">debug build</a> of Python 3.3 I had around. The surrounding code in <code>PyEval_FrameEx</code> is <pre><code> TARGET(LOAD_NAME) w = GETITEM(names, oparg); if ((v = f->f_locals) == NULL) { PyErr_Format(PyExc_SystemError, "no locals when loading %R", w); why = WHY_EXCEPTION; break; } if (PyDict_CheckExact(v)) { x = PyDict_GetItem(v, w); Py_XINCREF(x); } else { x = PyObject_GetItem(v, w); if (x == NULL && PyErr_Occurred()) { if (!PyErr_ExceptionMatches( PyExc_KeyError)) break; PyErr_Clear(); } } if (x == NULL) { x = PyDict_GetItem(f->f_globals, w); Py_XINCREF(x); if (x == NULL) { if (PyDict_CheckExact(f->f_builtins)) { x = PyDict_GetItem(f->f_builtins, w); if (x == NULL) { // below is the line where the PyExc_NameError will be properly formatted. format_exc_check_arg( PyExc_NameError, NAME_ERROR_MSG, w); break; } Py_INCREF(x); } else { x = PyObject_GetItem(f->f_builtins, w); if (x == NULL) { if (PyErr_ExceptionMatches(PyExc_KeyError)) format_exc_check_arg( PyExc_NameError, NAME_ERROR_MSG, w); break; } } } } PUSH(x); DISPATCH(); </code></pre> Note that two lines above it, <code>PyDict_GetItem(...)</code> will be the line trying to find <code>prnt</code> inside the builtin statements & functions (I deduce that from <code>f->builtins</code>, to which <code>w</code> is applied, <code>w</code> itself gotten from the second statement in the above code. Since that dictionary lookup will fail, <code>x == NULL</code> and the <code>NameError</code> is set and formatted. Hope this helps you further.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POWhere does Python gets its traceback information from?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
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. POWhere does Python gets its traceback information from?
 singulars
 PostTypePostTypeId
 PTQuestion
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTAcceptedByOriginator
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.