Skip to content
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

Headers are always written, even if there is already data present #1

Closed
jarvisms opened this issue Jul 3, 2019 · 1 comment

Comments

Projects
None yet
1 participant
@jarvisms
Copy link
Owner

commented Jul 3, 2019

Converters.py should only write headers to new/empty files but this is broken for the Bablake and Wellesbourne converters - i.e. they are always written regardless.

@jarvisms jarvisms self-assigned this Jul 3, 2019

@jarvisms jarvisms added the bug label Jul 3, 2019

jarvisms added a commit that referenced this issue Jul 10, 2019

Improvement to header detection
Solves issue #1 - Detection of existing file contents is now improved so it will know whether it should write a header.
@jarvisms

This comment has been minimized.

Copy link
Owner Author

commented Jul 10, 2019

Solved by 62dcda8.
Detection of existing file contents is now improved so it will know whether it should write a header.

@jarvisms jarvisms closed this Jul 10, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.