StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
10519403
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
1
CommunityOwnedDate
CreationDate
2012-05-09T15:38:39.797
FavoriteCount
0
LastActivityDate
2012-05-09T15:38:39.797
LastEditDate
LastEditorUserId
0
OwnerUserId
693085
ParentId
10518689
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
Half of one, six dozen of another. (Let that sink in. Ha ha.) But more seriously, do you honestly have multiple users on your system? These days, even Linux hosts tend to be for a single user, and where there are multiple user IDs they tend to be servers that run multiple processes under various quarantined user IDs. Given that, making life easier for all users isn't quite so relevant. On the other hand, multiple services each using Python may have conflicting requirements, rare as it may be that it boils down to even a required version of <code>pip</code>. Given that, I'd tend to prefer a global installation of virtualenv in order to make pristine quasi-installations of Python. Yet I'd like to point out one other idea: Buildout, <a href="http://www.buildout.org/" rel="nofollow">http://www.buildout.org/</a> Buildout does the same thing as virtualenv but by taking a remarkably different approach. You write a buildout configuration file (<code>buidout.cfg</code>) that lists what your various eggs are and how they'll be connected, and specify settings of "buildout recipes" that set up specialized situations (like a Django deployment, a Buildbot server, a Plone website, a Google app engine app, etc.). You then use your system Python to bootstrap the buildout, run it, and it generates an isolated setup—like a virtualenv. But the best part: it's repeatable. You can take the same <code>buildout.cfg</code> to another host and get the same setup. That's much harder to do with a virtualenv!
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POInstall pip and virtualenv, a chicken and the egg dilemma?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USnutjob
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. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. COthanks nutjob, that will make a delicious chicken omelette! Seriously, I do have several accounts on the server box (not the production, but the test environment!) - many developers go there and play to understand what's wrong. But your point is very fair, indeed I should favor the one user that runs my python services. I'll take a serious look at buildout too - I've heard it before, but never spent some time on it.
 singulars
 PostPostId
 PO
 UserUserId
 USStefano

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.