bzr should not give a traceback for a network error.
As far as the error itself:
1- some users may be firewalled or need a proxy; in that case we'd expect it to fail consistently
2- bzr or a library may be doing something strange that makes failures more likely (perhaps the timeout is unreasonably short?)
3- Launchpad may not be accepting the connection fast enough, and therefore it is a real timeout that they could potentially fix
bzr should not give a traceback for a network error.
As far as the error itself:
1- some users may be firewalled or need a proxy; in that case we'd expect it to fail consistently
2- bzr or a library may be doing something strange that makes failures more likely (perhaps the timeout is unreasonably short?)
3- Launchpad may not be accepting the connection fast enough, and therefore it is a real timeout that they could potentially fix