Heavy checkouts don't inherit nick

This "works" for lightweight because the nick is based on the branch path. Lightweight checkouts don't have another branch, and thus the only nick they can have is from the source.
Heavy checkouts have a local branch, and thus are defaulting to use it.

This could be fixed with just a check in Branch._get_nick/_set_nick to see if they are bound to another branch first.

I'm a little hesitant, because the way it is written requires actually connecting to the remote branch.
And Branch.get_master_branch() doesn't cache the master branch, so it is another full round trip (with another SSH connection opened, etc).

Further, what do you do if there *is* something set in the local branch.conf file? Just ignore it when you are bound and then use it when you are not?

Anyway, it can be argued that this is a feature, and not a bug. Since you did name the checkout something locally. But I can say that I have no use for this feature. (I always name my checkouts the same as the upstream).

Actually, I take that back, my repository sometimes looks like:

repo/dev/0.7

And my checkout becomes

work/dev-0.7/

So that when I commit I get the full "dev-0.7" rather than just "0.7".

Anyway, I would live either way, this should probably become a list discussion.

This was fixed as part of bug 230903 in bzr 1.9 as can be seen by the current script output:

Created a standalone tree (format: 2a)
     A A
 heavy A
 light A

However the behaviour is problematic for heavy checkouts of remote branches, see bug 882541 description.