Issue 154 in pydicom: write_file accepts file like object rather than just filename

[pyd...@googlecode.com]

Status: New
Owner: ----
Labels: Type-Defect Priority-Medium Difficulty-Medium

New issue 154 by agrothberg: write_file accepts file like object rather
than just filename
https://code.google.com/p/pydicom/issues/detail?id=154

write_file currently only takes a string path for the file name. It should
also be able to take a file like object. See:
https://github.com/cancan101/pydicom/commit/a28f149ce5b6a17e59be1ef225df734429cb32e8#diff-e08df3a1d02a03bb56c0ac1b5e47fb5aR336

--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

[pyd...@googlecode.com]

Comment #1 on issue 154 by darcy...@gmail.com: write_file accepts file

like object rather than just filename
https://code.google.com/p/pydicom/issues/detail?id=154

Good idea. But would be ideal to model on read_file which does a
try/except clause and closes the file if not supplied as a file object.

[pyd...@googlecode.com]

Comment #2 on issue 154 by agrothberg: write_file accepts file like object

rather than just filename
https://code.google.com/p/pydicom/issues/detail?id=154

I actually made the change already:
https://github.com/cancan101/pydicom/commit/53dc75976dcb28354f7f890d010779d5a5b40fcb

[pyd...@googlecode.com]

Updates:
Status: Fixed

Comment #3 on issue 154 by darcy...@gmail.com: write_file accepts file

like object rather than just filename
https://code.google.com/p/pydicom/issues/detail?id=154

This issue was closed by revision 28e93fd8f583.