StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
10262416
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2012-04-21T19:48:02.103
FavoriteCount
0
LastActivityDate
2012-04-21T19:55:55.813
LastEditDate
2012-04-21T19:55:55.813
LastEditorUserId
711085
OwnerUserId
711085
ParentId
10262278
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
If you are willing to modify your question a tiny bit, you can get away with this. IF the only entrypoints to your package are controlled; e.g. you only test your code by doing something like invoking <code>testsuite package/.../module.py</code> which will THEN you can make sure that the first thing you do is <code>import firstthing</code>, and in package/firstthing.py you have: <pre><code>import sys import os.path packageDir = os.path.split(__name__)[0] sys.path[:] = sys.path+[packageDir] # or maybe you want it first... </code></pre> The main caveat being that you will not be able to run python files without going through your entrypoints. I always want to do this for every project I write in python (to make relative imports work nicely), but I personally find this so inconvenient that I just give up. <hr> There is also a second alternative. It is not that unreasonable to specify that your package requires another package in the python path. This package could be a utility package which performs a major hack. For example if the name of the package was "x", you could do <code>import x</code> which would use the inspect module to perform reflection on the interpreter stack, letting you figure out which module you were importing it from. Then you could do a sort of "backwards os.walk" by going up parent directories until you found the root of your package (by checking for some special indicator file, or manifest, or something). Then the code would programatically perform the above modification of the python path via <code>sys.path</code>. It's the same as the above, but you have the liberty to do things like run any python file without having to go through an awful entrypoint. If you have extreme control over the shell environment, you can also just augment the $PYTHONPATH to include your package directory, but this is extremely fragile in many ways, and rather inelegant.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POBest way to import python module at the root of a package hierarchy from another module in the same package
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USninjagecko
UserOwnerUserId
1. USninjagecko
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.