Martijn Vermaat

The issue hasn't been resolved yet, so let's keep this one open. It contains some useful links and context and can still be used for general discussion. The specific implementation...

Support for writing is definitely immature, but #82 may be of interest to you.

I really like this idea! However, Aaron raises a valid concern. I think pandas really needs everything in memory (I don't know of a way to use numpy.memmap as a...

This is another example of something that could be fixed in a more general way using a proper parser, see #90 (although James' example code there does not implement this...

Indeed just using `json.dumps` would be quite easy and I don't really see a reason to wrap such a call in a PyVCF function. About the serialization, the problem with...

Yes, I like this a lot. It would be good to have an idea what kind of spec violations are out there and whether or not we can still parse...

Hi Sean, I'm a bit confused since the VCF record you quote is not a breakend and as such is not modeled using `_SingleBreakend`. Perhaps the error comes from another...

You're right, PR welcome :smile: The changelog file is [here](https://github.com/jamescasbon/PyVCF/blob/master/docs/HISTORY.rst). The git log for 0.6.7 to 0.6.8 is [here](https://github.com/jdoughertyii/PyVCF/compare/d1a9fdc...bfcedb9).

Keep in mind that for multi-base variants, the first base of REF and ALT will be the same (i.e., unchanged), so the affected region should not always include the REF...

I'm not sure what a MAF file is, but the `affected_start` and `affected_end` fields give you exactly the complete region (zero-based, open-ended) _on the reference_ that is affected (by all...