treat MemoryError as a special/environmental error

[Martin Pool]

There are various cases (see https://edge.launchpad.net/+search?field.text=bzr+memoryerror) where bzr can run out of memory and raise MemoryError.

In some ways these are all bugs but in practice they mean something else to the user: you just can't operate on such a big file (or whatever) with this version of bzr and this repo format.

We would, in a sense, like to get reports of these cases but at the moment we get more different bugs or dupes than are useful.

Therefore perhaps we should just show:

  bzr: out of memory

and perhaps log a traceback to .bzr.log.

Alternatively we could keep generating tracebacks to the screen (or to apport) but give a clearer "out of memory" error; MemoryError sounds like it could be an error in the memory or something.

[Martin Packman (gz)]

On IRC roryy discovered this was actually fixed already by poolie.