keywords: a problem and a question

M Busche spammymatt94 at
Mon Mar 4 17:33:34 UTC 2013

I've recently downloaded and installed this:

    bzr branch lp:bzr-keywords

Here's my bzr version info:

matt at meteor:cpp$ bzr --version
Bazaar (bzr) 2.5.1
  Python interpreter: /usr/bin/python 2.6.5
  Python standard library: /usr/lib/python2.6
  Platform: Linux-2.6.32-45-generic-i686-with-Ubuntu-10.04-lucid
  bzrlib: /usr/lib/pymodules/python2.6/bzrlib
  Bazaar configuration: /home/matt/.bazaar
  Bazaar log file: /home/matt/.bzr.log


Some keywords seem to work, and others do not.  Can anyone explain this result for my initial  commit-and-update cycle (where I was just trying out all the documented keywords)?  The first four tags are failing for some reason.

# $Date: (evaluation error) $
# $Committer: (evaluation error) $
# $Authors: (evaluation error) $
# $Revision-Id$
# $Path: cpp/SConstruct $
# $Filename: SConstruct $
# $Directory: cpp $
# $File-Id: sconstruct-20130130234613-01rcjondtjg69hz1-1 $
# $Now: Sat 2013-03-02 10:53:46 +0700 $
# $User: Matthew Busche <matt at> $


What I'd really like to be able to get in my file is the branch name, since for my setup the branch name is the software version number.  I went so far as to try to hack to add a new keyword that shells out via a Popen call to try to get the branch number from a bzr info call, but that fails in more way than one -- most significantly due to deadlock between the parent and child process.  Is there some internal python data structure from which i can read the branch name?  Failing this, I'm stuck with the prospect of using my build environment to do the substitutions -- which is just a bit more cumbersome.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the bazaar mailing list