[Distutils] Using setuptools

[Phillip J. Eby]

At 07:56 AM 11/25/2008 -0500, Val Schmidt wrote:
>Thanks!
>
>I also noticed that my SOURCES.txt file contains the contents of
>mymodulepy.egg-info (which got added to my subversion repository when
>I initially added the project directory). I suspect I don't want this
>either.

That depends on the project; in some cases, files are put manually 
into .egg-info, or there are reasons to keep the generated files 
under revision control.  The .egg-info directory is also 
automatically included in source distribution files.


>So does it seem like a reasonable working method to develop in one's
>subversion sandbox, check everything in, then checkout a copy of the
>project somewhere else to build distributions? This might help to make
>sure one doesn't inadvertently get the extra files and directories
>created during the build process into subversion and inadvertently in
>your distribution package.

I'm not clear on how you can accidentally get something into 
subversion.  In years of developing multiple packages with setuptools 
and subversion, I can't recall that I've ever accidentally typed "svn 
add build" or "svn add foobar.egg-info".  ;-)

Of course, when I start a new project, I start by svn add-ing the 
new, empty directory, and then explicitly add files as I go.  And 
when I start getting annoyed by svn stat showing a bunch of "?"'s, I 
go ahead and set svn:ignore as needed.

It's a lot less work than what you're describing, and even if I go 
too far with a wildcard add, there's always "svn rm" before 
checkin.  (I always svn diff before checkin, so it's hard for an 
accidental add to go unnoticed.)