StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POHow can I make setuptools ignore subversion inventory?
primarykey
Id
1129180
data
AcceptedAnswerId
1130598
AnswerCount
5
ClosedDate
CommentCount
3
CommunityOwnedDate
CreationDate
2009-07-15T03:00:19.547
FavoriteCount
4
LastActivityDate
2009-12-24T22:24:50.377
LastEditDate
LastEditorUserId
0
OwnerUserId
85360
ParentId
0
PostTypeId
1
Score
20
ViewCount
3327
LastEditorDisplayName
text
Body
When packaging a Python package with a setup.py that uses the setuptools: <pre><code>from setuptools import setup ... </code></pre> the source distribution created by: <pre><code>python setup.py sdist </code></pre> not only includes, as usual, the files specified in MANIFEST.in, but it also, gratuitously, includes all of the files that Subversion lists as being version controlled beneath the package directory. This is vastly annoying. Not only does it make it difficult to exercise any sort of explicit control over what files get distributed with my package, but it means that when I build my package following an "svn export" instead of an "svn checkout", the contents of my package might be quite different, since without the .svn metadata setuptools will make different choices about what to include. My question: how can I turn off this terrible behavior, so that "setuptools" treats my project the same way whether I'm using Subversion, or version control it's never heard of, or a bare tree created with "svn export" that I've created at the end of my project to make sure it builds cleanly somewhere besides my working directory? The best I have managed so far is an ugly monkey-patch: <pre><code>from setuptools.command import sdist del sdist.finders[:] </code></pre> But this is Python, not the jungle, so of course I want a better solution that involves no monkeys at all. How can I tame setuptools, turn off its magic, and have it behave sensibly by looking at the visible, predictable rules in my MANIFEST.py instead?
Tags
<python><packaging><setuptools><egg>
Title
How can I make setuptools ignore subversion inventory?
singulars
PostAcceptedAnswerId
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USBrandon Rhodes
plurals
PostLinksPostIdRelatedPostId
1. PL
 singulars
 LinkTypeLinkTypeId
 LTLinked
PostLinksRelatedPostIdPostId
1. PL
 singulars
 LinkTypeLinkTypeId
 LTLinked
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
2. PO
 singulars
 PostTypePostTypeId
 PTAnswer
3. PO
 singulars
 PostTypePostTypeId
 PTAnswer
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 POHow can I make setuptools ignore subversion inventory?
 UserUserId
 USluc
 VoteTypeVoteTypeId
 VTFavorite
2. VO
 singulars
 PostPostId
 POHow can I make setuptools ignore subversion inventory?
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
3. VO
 singulars
 PostPostId
 POHow can I make setuptools ignore subversion inventory?
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId

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.