M.-A. Lemburg wrote:
> The chance of two consecutive runs of sdist creating different
> archives is rather small, compared to those sources of error.
>
> That said, it's easy to get the upload command to use an
> already created distribution file for the upload: just
> add a new distutils command which sets .distribution.dist_files
> to what list of files you want to upload.
>
> This could also be added as an option to the distutils
> upload command, so that you can run:
>
> python setup.py upload --dist-files=dist/my-release-1.2.3.*
>
Here's a trick which will do the same without having to write
any new code:
First run:
python setup.py sdist --keep-temp
Then run your tests on the created archive locally.
Second run:
python setup.py sdist --dry-run upload
The second run won't build a new archive, it'll just upload the
already created archive to PyPI.
--
Marc-Andre Lemburg
eGenix.com
Professional Python Services directly from the Source (#1, May 16 2011)
>>> Python/Zope Consulting and Support ... http://www.egenix.com/
>>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/
>>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/
________________________________________________________________________
2011-06-20: EuroPython 2011, Florence, Italy 35 days to go
::: Try our new mxODBC.Connect Python Database Interface for free ! ::::
eGenix.com Software, Skills and Services GmbH Pastor-Loeh-Str.48
D-40764 Langenfeld, Germany. CEO Dipl.-Math. Marc-Andre Lemburg
Registered at Amtsgericht Duesseldorf: HRB 46611
http://www.egenix.com/company/contact/
_______________________________________________
Catalog-SIG mailing list
[email protected]
http://mail.python.org/mailman/listinfo/catalog-sig
