extra newline at end of OBO files written by oort #32
Comments
|
From HDie...@lbl.gov on January 17, 2012 13:11:39 OBO-Edit always appends an extra empty line at the end of an obo file. Thus the oboformat writer (and oort) does the same. This is an expected behavior. Please check with the FlyBase people. GO always had an empty newline at the end. They should be able to handle that. |
|
From HDie...@lbl.gov on September 18, 2012 15:26:11 Status: WontFix |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
From dosu...@gmail.com on January 17, 2012 03:21:46
What steps will reproduce the problem?
What is the expected output? What do you see instead?
This may not be specified in OBO format spec, but the default for OBO files produced by OE and other tools has always been for one return at the end. Having two returns confused local FlyBase curation checking software.
What version of the product are you using? On what operating system?
owltools -r433
Original issue: http://code.google.com/p/owltools/issues/detail?id=32
The text was updated successfully, but these errors were encountered: