[S3tools-bugs] s3cmd 1.0.0 dies when stdout is a pipe that gets closed

[Jay B. <ej...@ql...>]

I ran s3cmd ls s3://<bucket>/<prefix> | head and got the following
output, in addition to what I was looking for.  Looks like s3cmd just
doesn't trap the case of stdout being a pipe that gets closed while
being written to.  Let's hear it for python. :-)  I have not checked to
see whether this fixed in the latest version.  I'm just using the ubuntu
package with 12.04 LTS, which is still based on 1.0.0.

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
    An unexpected error has occurred.
  Please report the following lines to:
   s3t...@li...
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

Problem: IOError: [Errno 32] Broken pipe
S3cmd:   1.0.0

Traceback (most recent call last):
  File "/usr/bin/s3cmd", line 2006, in <module>
    main()
  File "/usr/bin/s3cmd", line 1950, in main
    cmd_func(args)
  File "/usr/bin/s3cmd", line 125, in cmd_ls
    subcmd_bucket_list(s3, uri)
  File "/usr/bin/s3cmd", line 183, in subcmd_bucket_list
    "uri": uri.compose_uri(bucket, object["Key"]),
  File "/usr/bin/s3cmd", line 33, in output
    sys.stdout.write(message + "\n")
  File "/usr/lib/python2.7/codecs.py", line 352, in write
    self.stream.write(data)
IOError: [Errno 32] Broken pipe

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
    An unexpected error has occurred.
    Please report the above lines to:
   s3t...@li...
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!