-
Notifications
You must be signed in to change notification settings - Fork 24
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ParseError #19
Comments
What kind of file are you parsing? Might it be a CPORT file? |
it has the extension .xpt so no |
I assumed it was probably v8 (you could’ve had a v8... support) or v9. Support would be nice. I could help if you want. Do you know where the v8/v9 specs are?
Jason Owens
jason.owens.we@gmail.com
… On Oct 16, 2018, at 4:30 PM, Michael Selik ***@***.***> wrote:
It's strange that the header would be empty like that. Have you checked the nearby lines?
You could be using a SAS v8 or v9 XPT file, which is a different format. No one has asked for support yet, but you could be the first.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.
|
I found the differences somewhere a while back. It looks like I jotted them down in the v89.py file https://github.com/selik/xport/blob/master/xport/v89.py |
BTW, I'm still toying with the project design. It's not set in stone if you think there's something better. |
I'm going to close this as a duplicate of #10. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
is the parse error you were referring to in your description "ParseError: header -- expected b'HEADER RECORD*******LIBRARY HEADER RECORD!!!!!!!', got b'\xd0\xcf\x11\xe0\xa1\xb1\x1a\xe1\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00>\x00\x03\x00\xfe\xff\t\x00\x06\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x01\x00\x00\x00'"
Potentially with custom bytes on the end there? If so, this library could use updating.
The text was updated successfully, but these errors were encountered: