Hash: SHA1

Baiju M wrote:
> Jim Fulton wrote:
>>  On Feb 15, 2007, at 3:02 AM, Baiju M wrote:
>>> Hi, I am not getting any changes (through checkins mailing list)
>>> made to zope eggs recently by 'alex' (committer id)
>>> alex, I read your commit mesage: "Remove setup.cfg.in, INSTALL.txt,
>>> CHANGES.txt, test.py, MANIFEST.in and README.txt because they are
>>> no longer needed."
>>  Could you remind me which package (or svn revision) you are refering
>>  to?
> *r72589, **r72588 and few others.*
>>> Why these files are no longer needed? test.py may not be required
>>> after buildout.
>>  I'll turn that around. What are they needed for? You should only
>>  need a setup.py and, if buildout is used, a buildout.cfg.
>>  The examples alex showed me seemed out of date with the current way
>>  of doing things.
>>  I particularly don't want setup.cfg.in, and MANIFEST.in as these
>>  aren't really necessary and tend to cause problems.
> Agreed.  Anyway, atleast we will be required a README.txt and CHANGES.txt

I would argue that those belong in the *package*, not in the "building"
directory (the one containing 'setup.py'), because they are relelvant to
users of the built egg, not just to the developer who checks out the
whole thing.

I know that distutils / setuptools complain if they find no 'README.txt
' next to setup.py:  I ususally have a nearly empty one pointing "down"
to the real one.

- --
Tres Seaver          +1 540-429-0999          [EMAIL PROTECTED]
Palladion Software   "Excellence by Design"    http://palladion.com
Version: GnuPG v1.4.2.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

Zope3-dev mailing list
Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com

Reply via email to