===> PyVCF3 <<===

[dridk]

PYVCF3 is available here :
https://pypi.org/project/PyVCF3/

As the project is not maintained anymore, but very used... I suggest to make a fork and rename the project as "PyVCF2" on pypi.
We will finally be able merge the pull requests.
Who's motivated?

[dridk]

I suggest to start from the last critical fix

https://github.com/ousamg/[email protected]

[dridk]

I did one here named "PyVCF3" . Those one works on python3 only :

https://pypi.org/project/PyVCF3/1.0.0/

I m going to merge some pull request right now.

[iamh2o]

I'll start using that and have some fixes I can prob add. This has been abandoned a long time, but still one of the better VCF parsers. Thanks for rescuing it.

[dridk]

No problem ! I already merge some pull request and did some improvement

[pkMyt1]

@dridk Thank you. I don't work with vcf files that often and just found the bug in the original version. Unfortunately, maintaining repos is a drudge.

[gdurif]

Thank you very much @dridk

Could you open the issues on your repository? I encounter #337 even with PyVCF3 (edit: the problem was the VCF file and not pyvcf)

[dridk]

you can rate the project to make it known by other

[mbhall88]

Could you open the issues on your repository?

Agreed, this would be very handy.

I've also created a recipe on bioconda for pyvcf3 bioconda/bioconda-recipes#34505

[dridk]

I just open the issues page on pyvcf3 ! It was disabled, sorry...
dridk#1