StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
18385942
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-08-22T16:20:42.687
FavoriteCount
0
LastActivityDate
2013-08-22T16:30:54.593
LastEditDate
2013-08-22T16:30:54.593
LastEditorUserId
562106
OwnerUserId
562106
ParentId
2627731
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
I use scons to generate a setup.py file. So I created a template called setup.py.in and use scons to expand the template to generate setup.py. Here are some links to my project that does this: <a href="http://sourceforge.net/p/nsound/code/756/tree/branch/nsound-dev-weegreenblobbie/setup.py.in" rel="nofollow">setup.py.in template</a> <a href="http://sourceforge.net/p/nsound/code/756/tree/branch/nsound-dev-weegreenblobbie/SConstruct" rel="nofollow">The SConstruct</a> This computes a dictionary of key, value pairs to substitute into the setup.py.in template to generate setup.py. So the end user does two things: <pre><code>scons setup.py python setup.py install </code></pre> Warning: my sconstruct stuff is a bit messy as I wrote it awhile ago, but it should demonstrate the concept. If you learn how to write proper scons tools, then this can be transformed into a single target, for example: <pre><code>scons --pymod </code></pre> Here is a scons tool the generates a Python wrapper with SWIG: <pre><code>import SCons.Action from SCons.Script import EnsureSConsVersion SCons.Script.EnsureSConsVersion(0,96,92) SwigGenAction = SCons.Action.Action('$SWIGGENCOM', '$SWIGGENCOMSTR') def emitter(target, source, env): """ Add dependency from target to source """ env.Depends(target, source) return target, source def generate(env): """ Add builders and construction variables for the SwigGen builder. """ if 'SWIGCOM' not in env: raise SystemError("SCons build environment could not detect tool: swig") bld = env.Builder( action = SwigGenAction, emitter = emitter, target_factory = env.fs.File) env['BUILDERS']['SwigGen'] = bld env['SWIGGENCOM'] = env['SWIGCOM'] def exists(env): return env.Detect('swig') </code></pre> Now from your SConstruct file, you can generate the wrapper code: <pre><code>foobar_cc = env.SwigGen("foobar_wrap.cc", "foobar.i") </code></pre> If you modify foobar.i it will regenerate foobar_wrap.cc. Once you have this, you can write other tools for actually executing python setup.py install for you, so when --pymod is provided it will build the python module.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POUsing SCons as a build engine for distutils
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USNick
UserOwnerUserId
1. USNick
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.