StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
18000022
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-08-01T16:50:26.637
FavoriteCount
0
LastActivityDate
2013-08-01T16:55:56.333
LastEditDate
2013-08-01T16:55:56.333
LastEditorUserId
654162
OwnerUserId
654162
ParentId
17998193
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
I wrote a more concise, minimal example to reproduce your problem: a.py <pre class="lang-python prettyprint-override"><code>import b class A(object): def get_magic_number_from_b(self): return b.magic_number() </code></pre> b.py <pre class="lang-python prettyprint-override"><code>import a def magic_number(): return 42 class B(a.A): pass </code></pre> Similar to your example, class B in module b inherits from class A in module a. At the same time, class A needs some functionality from module b to perform its function (in general, you should try to avoid this if you can). Now, when you import module a, Python will import module b as well. This fails with an <code>AttributeError</code> exception since the class b.B depends explicitly on a.A, which is not yet defined at the time when the <code>import b</code> statement is executed. To solve this issue, you can either move the <code>import b</code> statement behind the definition of A, like this: <pre><code>class A(object): def get_magic_number_from_b(self): return b.magic_number() import b </code></pre> , or you move it to within the definition of the function that depends on the functionality from module b, like this: <pre><code>class A(object): def get_magic_number_from_b(self): import b return b.magic_number() </code></pre> Alternatively, you can make sure that you always import module <code>b</code> before module <code>a</code>, which will also solve the problem (since a has no import-time dependencies on b).
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POPython - Circular import with super function calling method
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USThePhysicist
UserOwnerUserId
1. USThePhysicist
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POPython - Circular import with super function calling method
 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
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
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.