On Tue, Apr 07, 2009 at 07:20:11AM +0200, Lennart Regebro wrote: > OK, here is a usecase. I have a directoy with a module, foo.bar. I > have also in that directory saved a project file from my IDE, because > naturally I save a project file into the directory of every project I > have. But since that's not a part of the module itself I never check > it in. > > My friend Bobo, however, does not use an IDE, and does not create a > project file. > > In case number one, I specify the files to be included with a wildcard. > > In case number two, I do not specify the files to be included at all, > but let sdist determine the files by looking at which files are > version controlled. > > Now, in which of these cases will the sdist created by me an d by Bobo > be identical? Right. In the one where the file list is determined by > which files are version controlled. Can we then really say that this > case is more dependent on the environment?
Consider a different use case: my friend's friend Alice does not like
svn. She uses git-svn to get a local git repository containing a copy
of the subversion code. She then uses the usual 'python setup.py sdist'
build process. It produces a broken distribution (silently) because
setuptools doesn't support git, and Alice didn't know she had to install
a plugin.
Users don't expect version control system metadata to have an influence
on the build process (other than recording the revision number/ID
somewhere in the built package).
Marius Gedminas
--
TCP_SeqNum - The 32-bit Sequence Number, encoded as an ASCII string
representing the hex value of the Sequence number. This field
MUST be sent as lower case because it is not urgent.
-- RFC 3093
signature.asc
Description: Digital signature
_______________________________________________ Distutils-SIG maillist - [email protected] http://mail.python.org/mailman/listinfo/distutils-sig
