Fix errors creating SigMFFile objects that do not have datatype set #180
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This prevents users from setting a datafile, which queries information that requires the datatype meta field to be set. It also generates a more useful exception when the dtype parser is run with None input.
Closes #178
@Teque5 I solved this in a slightly different way than described in #178 because that prevents constructing a plain
SigMFFile()object, which is reasonable and people might be doing this already. This only changes behavior that currently causes an obscure error.