StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
20277005
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
2
CommunityOwnedDate
CreationDate
2013-11-29T01:20:09.920
FavoriteCount
0
LastActivityDate
2013-11-29T01:20:09.920
LastEditDate
LastEditorUserId
0
OwnerUserId
3047642
ParentId
20276343
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
The answer to that question lies in Python's distinction between unbound method and bound methods. When you define a method, it's unbound: it can operate on any instance of the class, and it is, in fact, nothing more than a function whose first argument is named self (and even then, it's a convention) and a little bit of checking so you don't do truly horrible things with them. <pre><code>class Foo(object): def my_method(self, arg): print "self:", self print "arg:", arg a = Foo() print Foo.my_method(a, 2) # self: self: <__main__.Foo object at 0x000000000219DE10> # arg: 2 # You could, in theory, do that, but Python complains because it values the sanity # of the people who will have to maintain your code :p print Foo.my_method(1, 2) # TypeError: unbound method my_method() must be called with Foo instance as first argument (got int instance instead) </code></pre> So far, nothing special. However, Python has a bit of magic when we call a method not on the class itself (as is done above), but on an instance of that class (that is, on an object). <pre><code>a.my_method(2) # self: <__main__.Foo object at 0x000000000219DE10> # arg: 2 </code></pre> Notice how suddenly you only have to supply <code>arg</code> to the method, even though it's defined with two arguments? That's because <code>a.my_method</code> is a bound method: it's the <code>my_method</code> method of the <code>a</code> object, not that of the <code>Foo</code> class. It is bound to that particular instance, and has a reference to that particular object in it (if you look at <code>dir(a.my_method)</code>, you'll notice it has a <code>im_self</code> attribute). However, in your example, if you were to add a <code>print self</code> statement in <code>func1</code>, it would print <code>foo0</code> instead of <code>foo0.child</code>. That's because the "binding" happens not when you call the method (<code>foo0.child.secondMethod()</code>), but simply when you reference it (<code>foo0.func1</code>). More importantly, it only ever happens when you reference a method that you defined on a class. So in your example, <code>foo0.child.secondMethod = foo0.func1</code> references <code>foo0</code>'s <code>func1</code> method (which gives you a bound method of <code>foo0</code>), but no magic is performed in the assignment itself. It's simply setting an attribute of <code>foo0.child</code>. Does that make sense?
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POself reference in monkey patched python class
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USMax Noel
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POself reference in monkey patched python class
 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
 VTAcceptedByOriginator
CommentsPostId
1. COthis used to catch me out a lot. If your asking, "why bound methods?" as far as I can tell it solely for those times when you might pass an object's method as an argument, or store it in a variable to be called later. Then a bound method will remember who its object (self) is.
 singulars
 PostPostId
 PO
 UserUserId
 USCyclone

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.