Glyph Lefkowitz wrote: > pkg_resources is not a good way to get access to this information programmatically because it's decoupled from the mechanism used to actually load the code (i.e. importing). So there's the opportunity for desynchronization.
+1. In Tahoe-LAFS we consider pkg_resources to be an unreliable method of getting version numbers, having been bitten by cases where the returned version was simply wrong (http://tahoe-lafs.org/trac/tahoe-lafs/ticket/1258#comment:8).
Glyph Lefkowitz wrote:
> pkg_resources is not a good way to get access to this information programmatically because it's decoupled from the mechanism used to actually load the code (i.e. importing). So there's the opportunity for desynchronization.
+1. In Tahoe-LAFS we consider pkg_resources to be an unreliable method of getting version numbers, having been bitten by cases where the returned version was simply wrong (http:// tahoe-lafs. org/trac/ tahoe-lafs/ ticket/ 1258#comment: 8).