[Catalog-sig] PyPI's external packages

Tres Seaver tseaver at palladion.com
Mon May 16 02:11:16 CEST 2011


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 05/13/2011 01:12 PM, exarkun at twistedmatrix.com wrote:
> 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.

ISTM that if you run 'python setup.py sdist' a second time and get a
different result (without changing any included files), then you have a
built-in quality problem *in your setup.py.*



Tres.
- -- 
===================================================================
Tres Seaver          +1 540-429-0999          tseaver at palladion.com
Palladion Software   "Excellence by Design"    http://palladion.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk3Qa6QACgkQ+gerLs4ltQ7tawCgjGf3C3Uvu8VB7Yp9ffr59gUW
bJcAniOrvsiPRA8yhsyqNon1i653wHkv
=1Jon
-----END PGP SIGNATURE-----



More information about the Catalog-SIG mailing list