io: Parse metadata with C engine, restrict to either CSV or TSV by victorlin · Pull Request #812 · nextstrain/augur (original) (raw)
victorlin changed the title
io: Parse metadata with C engine and tab separator io: Parse metadata with C engine, restrict to either CSV or TSV
victorlin marked this pull request as ready for review
Previously, the delimiter could be anything arbitrary. However, all Augur subcommands that use this function only advertise compatibility with CSV and TSV. I don't think there's a good reason to support arbitrary delimiters.
The python engine was only used to detect the delimiter. Now that the delimiter is detected separately, use the C engine since it is faster.
Avoids re-defining this list at each use case and prevents them from getting out of sync.
victorlin deleted the victorlin/io/use-c-engine-parsing branch
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.Learn more about bidirectional Unicode characters
[ Show hidden characters]({{ revealButtonHref }})