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.

Sign up for GitHub

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

Jump to bottom

Move away from pyvcf #142

Closed
mbhall88 opened this issue Nov 18, 2021 · 0 comments · Fixed by #146
Closed

Move away from pyvcf #142

mbhall88 opened this issue Nov 18, 2021 · 0 comments · Fixed by #146

Comments

@mbhall88
Copy link
Member

It seems appveyor is failing and tl;dr I think it is because of jamescasbon/PyVCF#3. Ultimately, this is a bigger issue and we should look to move away from pyvcf (which seems to not be maintained anymore - no commits since 2017). I'll open a separate issue for this.

Originally posted by @mbhall88 in #138 (comment)

My suggestion would be for https://github.com/brentp/cyvcf2 as it is actively maintained, fast, and I have a lot of experience with it.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Switch from pyvcf to cyvcf2 for VCF parsing mbhall88/mykrobe
1 participant
@mbhall88