Closed will-moore closed 4 years ago
From the former issue it looks like we need to specify utf-8
encoding wherever appropriate similarly to https://github.com/ome/omero-py/pull/110. Looking at https://python-future.org/compatible_idioms.html#file-io-with-open, it might be possible to have a unified Py2/Py3 idiom:
from io import open
...
with open(file_name, 'w', encoding='utf-8') as csv_file:
...
The latter issue is related to the fact the omero-metadata
plugins needs to be upgraded to Python 3 - see in-progress work in https://github.com/ome/omero-metadata/pull/36
There was a workaround in https://github.com/ome/omero-scripts/commit/d9119def3237feefe45b7972e024eb159102d98d to only write encoded bytes to csv, because writing unicode to csv fails on the py3-ci server due to lack of UTF-8 encoding as described https://github.com/ome/omero-figure/pull/343#issuecomment-565426063 and https://github.com/ome/omero-figure/pull/351#issuecomment-565392138
Batch_ROI_Export failing because of unicode um characters at
Populate_Metadata.py - opening script dialog gives: