[MERGE] dont stacktrace on bad plugin versions
Guillermo Gonzalez
guillo.gonzo at gmail.com
Wed Oct 15 21:10:11 BST 2008
Hi
On Wed, Oct 15, 2008 at 4:51 PM, Marius Kruger <amanic at gmail.com> wrote:
> Hi,
>
> For background I did:
> $ bzr branches bzr+https://me@someserver/bzr/myrepo/
> poc/EBRClientPrototype.dev
>
> which worked fine. then
> $ bzr branches bzr+https://me@someserver/bzr/
>
> threw a stack trace, but when it tries to make a message with all the plugin
> versions
> for the user to be able to report a bug, it trows another exception :(
>
> It turns out that one of my plugins (xmloutput) has a non-standard version
> number:
> version_info = (0, 9, 0, 'dev')
> which looks fine if you dont know better.
>
Ups, my fault. sorry for the wrong version_info.
> I could not find any place in the documentation which specifies what this
> version
> number should contain, so I added a little something.
>
version_info numbering scheme is defined from python sys.version_info,
> I also thought that it'll be much nicer of us to rather format whatever is
> in there
> in stead of throwing our toys out of the cot.
maybe we should add this to the documentation?
>
> regards
> marius
>
Regards,
--Guillermo
More information about the bazaar
mailing list