On Wed, 2011-03-23 at 16:59 -0400, Mark Sienkiewicz wrote: > Ronny Pfannschmidt wrote: > > Hi, > > > > i'd like to propose making the work-flow of creating releases by just > > pushing vcs tags to a ci system as easy as possible > > > > personally all i ever want to do to release a new version is:: > > > > $vcs tag $version > > $vcs push > > > > currently that would require various nasty hacks to get the version > > meta-data static on sdist and to grab the version number in a setup hook > > > > Maybe you should go the other way: Put the version number in your > source code. Make a short script that picks out the version number and > constructs a tag name for the vcs. Raise an error if the tag already > exists. >
i never ever want to have a version number of the project outside of a vcs tag inside the vcs repo also its convient to automatically imply different version numbers for each commit (which includes a dev marker + a revision id) > This method is easy to implement for your project alone, it is easy to > distribute to others who want to do the same thing, and there are no > nasty hacks involved. For example, > > % python tagdist.py > You didn't change the version number! > % emacs setup.cfg > % python tagdist.py > Tagging release 0.0.2 > % > > If you find it works well in practice, you might then propose to move > the script into "python setup.py tagdist".
signature.asc
Description: This is a digitally signed message part
_______________________________________________ Distutils-SIG maillist - [email protected] http://mail.python.org/mailman/listinfo/distutils-sig
