Automatically update setup.py version on every SVN commit

Question

We are deploying Plone add-ons as development eggs with buildout. The eggs are pushed to the production as source code checkouts using Mr. Developer buildout recipe and .egg packaging is not done in any point.

What would be best way to automatically update setup.py version stamp on every SVN commit to SVN release number or timestamp? This would give some quick info of tracking of different packages.

Distutils seem to offer some kind of magic version stamping mechanism, but I did not found any reference documentation how this should be used.

Duplicate of getting-svn-revision-number-into-a-program-automatically ?! — gecco
– gecco, Commented Dec 13, 2011 at 10:16

maurits · Accepted Answer · 2011-12-13 12:17:13Z

6

Add something like this in setup.cfg:

[egg_info]
tag_build = .dev
tag_svn_revision = 1

This only works for subversion of course; not sure if there are alternatives for other vcs. This file may still be added by default by some of the ZopeSkel templates. Some plone packages have it too; Wichert Akkerman is/was a fan of it.

Note that you do need to run bin/buildout or python setup.py egg_info every time to commit something, else the version info in the egg-info directory is not updated.

answered Dec 13, 2011 at 12:17

maurits

2,39513 silver badges17 bronze badges

Sign up to request clarification or add additional context in comments.

1 Comment

Reinout van Rees Over a year ago

Watch out, though, when releasing the package to pypi if you use this method. Don't forget to remove the lines from setup.cfg before releasing. There are too many mypackage-1.2-r1234.tar.gz packages...

gecco · Accepted Answer · 2011-12-13 10:28:54Z

1

You can use simply the SVN Keywords, like

__version__ = "$Rev:$"

SVN automatically changes with this keyword the version on every filechange respectively commit.

edited Dec 13, 2011 at 10:28

gecco

19k11 gold badges53 silver badges68 bronze badges

answered Dec 13, 2011 at 9:36

Themerius

1,9111 gold badge19 silver badges33 bronze badges

2 Comments

Reinout van Rees Over a year ago

This will work fine for every commit to setup.py (assuming you put this line into setup.py). It won't update itself when you commit another file.

Lazy Badger Over a year ago

1 - Use correct SVN-keyword, for revision it's $Revision$, not your scrap 2 - expanded revision keyword isn't pure numeric revision only, it seems like such $Revision: 1132 $ and require post-processing 3 - Keyword show file's last-change revision, not repo-wide last-commit revision. Bad, you must redone your homework and RTFM

Lazy Badger · Accepted Answer · 2011-12-13 19:30:32Z

0

What would be best way to automatically update setup.py version stamp on every SVN commit to SVN release number or timestamp?

If

build process can execute some actions (I'm too lazy to read buildout recipe)
using additional Windows-only tools isn't strong "no-no" for you

you can consider to use SubWCRev cli-tool from TortoiseSVN package. It (slightly) change current workflow:

instead of real setup.py repository store template of setup.py, where dynamic part of data replaced by SubWCRev-keywords (they can handle revision, date in free form)
Every build-process have to regenerate actual setup.py by calling subwcrev against (local) working copy with predefined setup-template

edited Dec 13, 2011 at 19:30

answered Dec 13, 2011 at 15:29

Lazy Badger

98.1k9 gold badges83 silver badges113 bronze badges

3 Comments

Mikko Ohtamaa Over a year ago

The toolchain was explained in the question and it is not Windows based toolchain, luckily.

Lazy Badger Over a year ago

"using Mr. Developer buildout recipe" tells me nothing, BTW

Mikko Ohtamaa Over a year ago

Well then you might not be part of the audience who the question was targeted, but thank you for the suggestion anyway :)

Collectives™ on Stack Overflow

Automatically update setup.py version on every SVN commit

3 Answers 3

1 Comment

2 Comments

3 Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

3 Answers 3

1 Comment

2 Comments

3 Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related