There's a regression in the recent addition of transparent compression in userio module (#345). The resulting files in events_home silently fail during writes for the compressed cases due to a subtle bytes vs str issue for gzip and bz2 file handles, when using mode strings without a specific binary or text marker. They default to open in binary mode in that case, which breaks writing of plain strings with an error like:
memoryview: a bytes-like object is required, not 'str'
There's a regression in the recent addition of transparent compression in userio module (#345). The resulting files in events_home silently fail during writes for the compressed cases due to a subtle bytes vs str issue for gzip and bz2 file handles, when using mode strings without a specific binary or text marker. They default to open in binary mode in that case, which breaks writing of plain strings with an error like:
memoryview: a bytes-like object is required, not 'str'