You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 4, 2020. It is now read-only.
pymarc.field.Field.__str__() uses native str as the arguments to self.data.replace, but in a RawField, data is a bytes object, so we get TypeError: 'str' does not support the buffer interface
RawField should probably have its own implementation of __str__, although it's unclear to me how we should represent a field with an unknown encoding as text...
The text was updated successfully, but these errors were encountered:
It's not, and looking deeper into it I can't see a good way to represent an arbitrary byte in MarcBreaker (http://www.loc.gov/marc/makrbrkr.html#mechanics) format especially since "" means "space" in the 00x fields, so "\x" doesn't work. Of course, these fields should be all ASCII, but the whole point of RawField is that sometimes they're not in the real world.
I suppose I could see how MarcEdit treats such a pathological record.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
pymarc.field.Field.__str__()
uses native str as the arguments toself.data.replace
, but in a RawField,data
is a bytes object, so we getTypeError: 'str' does not support the buffer interface
RawField
should probably have its own implementation of__str__
, although it's unclear to me how we should represent a field with an unknown encoding as text...The text was updated successfully, but these errors were encountered: