[Zope3-dev] Re: faulty releases and pypi access [update]
Philipp von Weitershausen
philipp at weitershausen.de
Wed Sep 26 15:32:30 EDT 2007
Jim Fulton wrote:
> On Sep 26, 2007, at 1:18 PM, Fred Drake wrote:
>
>> On 9/26/07, Martijn Faassen <faassen at startifact.com> wrote:
>>> What does one need to tell setup.py to make sure CHANGES.txt is
>>> available? I understand it isn't by default, then? Hm, it does appear to
>>> be there by default. I checked grok 0.10's tgz and it's there, and we
>>> didn't do anything special.
>>
>> Do you mean available in the unpacked sdist, or as part of the
>> installation? I don't think any of README, README.txt, CHANGES,
>> CHANGES.txt (from the root of the distribution, not from inside the
>> package) are actually installed. If they are, I'd love to know where.
>
> By default READM(.txt) is installed in a source distribution. Anything
> else in the root (aside from setup.py of course and source files
> themselves) aren't without extra setup chants. (These chants can be
> figured out with some effort. I never remember them, so, if I want to
> do something like this, I have to figure them out again or try to find
> an example with them.)
Actually, no package data is ever included unless you're either
* working from an svn checkout, in which case setuptools will use the
list of which files are in svn and which aren't as a hint of what to
include and what not
* creating a MANIFEST.in file to tell setuptools what to include explicitly.
--
http://worldcookery.com -- Professional Zope documentation and training
More information about the Zope3-dev
mailing list