[prev in list] [next in list] [prev in thread] [next in thread]
List: python-distutils-sig
Subject: Re: [Distutils] Regeneration of source manifest
From: "Arve Knudsen" <arve.knudsen () gmail ! com>
Date: 2007-07-26 19:47:56
Message-ID: a0d6258d0707261247l3b886133q87d347eb165461ac () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
On 7/26/07, Phillip J. Eby <pje@telecommunity.com> wrote:
>
> At 10:51 PM 7/25/2007 +0200, Arve Knudsen wrote:
> >I take it there is no interest in fixing this problem? Or is it
> >simply too much hassle??
> >
> >Arve
> >
> >On 7/10/07, Arve Knudsen <<mailto:arve.knudsen@gmail.com>
> >arve.knudsen@gmail.com> wrote:
> >Hello
> >
> >As far as I can tell setuptools does not always regenerate the
> >source manifest when MANIFEST.in changes, contrary to what the
> >documentation says. That is, if I add a directive to exclude files
> >with the .txt extension to MANIFEST.in (after having previously
> >including them), and run the sdist command, such files are still
> >included. I have to remove the .egg-info for things to work as
> >expected. This must clearly be a bug?
> >
> >Regards,
> >Arve Knudsen
>
> Your email got lost in the flurry of PyPI-related emails. I am
> looking at the code and don't see how this condition could be
> produced, at least not the way you seem to be describing it, because
> the template is processed after the old filelist is read in. So if
> there are exclusion commands in the template, these should *always*
> be applied to the resulting SOURCES.txt.
>
> Could you give me the exact old MANIFEST.in contents, the new
> MANIFEST.in contents, and the egg-info/SOURCES.txt?
>
> Better yet, can you give me a small setup.py and steps that I can use
> to reproduce the problem?
Sorry, I can't seem to reproduce the exact problem (it doesn't help that I
don't recollect the exact case). What I do notice when testing however, is
that if I first add a directive in MANIFEST.in to include ez_setup.py and
run sdist, remove the directive and run sdist again, ez_setup.py is still in
SOURCES.txt. So it seems that sdist somehow remembers previous include
directives for files that aren't included by default.
Arve
[Attachment #5 (text/html)]
On 7/26/07, <b class="gmail_sendername">Phillip J. Eby</b> <<a \
href="mailto:pje@telecommunity.com">pje@telecommunity.com</a>> wrote:<div><span \
class="gmail_quote"></span><blockquote class="gmail_quote" style="border-left: 1px \
solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> At 10:51 PM \
7/25/2007 +0200, Arve Knudsen wrote:<br>>I take it there is no interest in fixing \
this problem? Or is it<br>>simply too much \
hassle??<br>><br>>Arve<br>><br>>On 7/10/07, Arve Knudsen <<mailto: \
<a href="mailto:arve.knudsen@gmail.com">arve.knudsen@gmail.com</a>><br>><a \
href="mailto:arve.knudsen@gmail.com">arve.knudsen@gmail.com</a>> \
wrote:<br>>Hello<br>><br>>As far as I can tell setuptools does not always \
regenerate the <br>>source manifest when MANIFEST.in changes, contrary to what \
the<br>>documentation says. That is, if I add a directive to exclude \
files<br>>with the .txt extension to MANIFEST.in (after having \
previously<br>>including them), and run the sdist command, such files are still \
<br>>included. I have to remove the .egg-info for things to work \
as<br>>expected. This must clearly be a bug?<br>><br>>Regards,<br>>Arve \
Knudsen<br><br>Your email got lost in the flurry of PyPI-related emails. I \
am <br>looking at the code and don't see how this condition could be<br>produced, \
at least not the way you seem to be describing it, because<br>the template is \
processed after the old filelist is read in. So if<br>there are exclusion \
commands in the template, these should *always* <br>be applied to the resulting \
SOURCES.txt.<br><br>Could you give me the exact old MANIFEST.in contents, the \
new<br>MANIFEST.in contents, and the egg-info/SOURCES.txt?<br><br>Better yet, can you \
give me a small setup.py and steps that I can use <br>to reproduce the \
problem?</blockquote><div><br>Sorry, I can't seem to reproduce the exact problem \
(it doesn't help that I don't recollect the exact case). What I do notice \
when testing however, is that if I first add a directive in MANIFEST.in to include \
ez_setup.py and run sdist, remove the directive and run sdist again, ez_setup.py is \
still in SOURCES.txt. So it seems that sdist somehow remembers previous include \
directives for files that aren't included by default. \
<br><br>Arve<br></div><br></div>
_______________________________________________
Distutils-SIG maillist - Distutils-SIG@python.org
http://mail.python.org/mailman/listinfo/distutils-sig
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic