There is no version attribute anywhere in subunit

Bug #531667 reported by Jean-Paul Calderone
20
This bug affects 3 people
Affects Status Importance Assigned to Milestone
subunit
Fix Released
Wishlist
Robert Collins

Bug Description

It's very useful to be able to programmatically inspect the version of a package. There is apparently no version information anywhere in subunit, though. It would be nice if some were added.

Revision history for this message
Robert Collins (lifeless) wrote :

I agree; I do this on nearly all new packages; subunit has been around for a while is all.

Changed in subunit:
status: New → Triaged
importance: Undecided → Wishlist
Revision history for this message
Jelmer Vernooij (jelmer) wrote :

I might have a look at this later, but posting here before I forget or if anybody else beats me to it:

23:41 < lifeless> have a look at testrepository or whatnot for style
23:41 < lifeless> basically I'd like it generated from configure.ac
23:41 < lifeless> uhm, as __init__ is rather big, perhaps a version.py.in approach
23:41 < lifeless> and then in __init__, from _version import __version__

Revision history for this message
Martin Packman (gz) wrote :

Not having a version means I have to do some funny hacks in:
<https://code.launchpad.net/~gz/bzr/trivial_subunit_unexpectedly_correct/+merge/61470>

I'd prefer to require a minimum subunit python module version some time after "subunit next" is released.

Revision history for this message
Robert Collins (lifeless) wrote :

Patches gracefully etc etc

Revision history for this message
Robert Collins (lifeless) wrote :

There has been one for a bit; I don't recall when we added it.

Changed in subunit:
assignee: nobody → Robert Collins (lifeless)
milestone: none → next
Changed in subunit:
status: Triaged → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.