This does appear to be in bzr-builddeb because the DistributionBranch.has_version() calls _has_version() and that is the one doing the graph ancestry checks.
Also note that .has_version() potentially searches the graph 3 times, using 3 different graph objects in a single call.
This does appear to be in bzr-builddeb because the DistributionBra nch.has_ version( ) calls _has_version() and that is the one doing the graph ancestry checks.
Also note that .has_version() potentially searches the graph 3 times, using 3 different graph objects in a single call.