editor backup file left over after bzr commit

When doing a raw "bzr commit" with no -m, an editor is fired up on a temporary file with a name like "bzr_log.1ySd21". Once this is saved, the editor exits, and commit is successful, the file is deleted. However, many editors leave a backup file with a trailing tilde lying around afterward, e.g. "bzr_log.1ySd21~".

Since this type of backup file is left by most common UNIX editors (e.g. vim, emacs, xemacs, nano, nedit, kate, etc) it makes sense that bzr would go ahead and remove not just it's temporary file, but also that filename+"~".

I suppose there could be some (crazy?) concern that maybe the USER has a REAL file that they want to KEEP named "bzr_log.something~" and this would potentially overwrite it. To address that possible concern, keep in mind that already this is a "problem": if you have a file named "something~" and you pull up any UNIX editor on a file named "something", it will clobber the original "something~" file. So bzr deleting this file is no worse than what it already does. But see another idea below:

An alternate -- and safer -- method that would be to create a unique directory "bzr_log.whatever" and put the log file in there, e.g. "bzr_log.whatever/log" and then remove the directory and it's contents afterward, which would get rid of the pesky "~" backup file, would prevent any possible user data clobbering, and would be robust to any sort of editor backup naming scheme.