[Catalog-sig] PyPI's external packages

[exarkun at twistedmatrix.com]

On 03:21 pm, merwok at netwok.org wrote:
>Le 12/05/2011 21:04, exarkun at twistedmatrix.com a écrit :
>>On 03:57 pm, ziade.tarek at gmail.com wrote:
>>>[...]
>>>I'll definitely do something in distutils2 but maybe someone has a
>>>better idea ?
>>Make it easier to upload packages to PyPI.  For example, [...]
>>make "upload" work even if the package files exist on
>>the filesystem somewhere already.
>
>You 19re referring to the fact that  1Cupload 1D won 19t push files already
>present in dist/, right?

More or less, yes.
>I don 19t know whether this was a design choice
>of Martin or merely done for code simplicity, but currently the command
>will only push files that are products of a command run from the same
>command line, e.g.  1Csdist upload 1D.  If you run  1Csdist and then  1Csdist
>upload 1D, is the sdist recreated even though there have been no changes
>to the files?

Yes, the sdist is recreated.
>
>If no, having to run  1Csdist upload 1D is not inefficient, and makes you 
>be
>explicit about the files you want to push, which is IMO good.  Do you 
>agree?
>
>If yes, I think it 19s a bug.

I'm not concerned about the efficiency, though.  I'm concerned about the 
quality of the build.  I want to generate a release, *test it*, and then 
upload it.  Being forced to generate it and upload it at the same time 
gets in the way of this.

Jean-Paul