Ah,

I understand. I was aiming for a more strict definition of equal, which after more consideration, may be less practical than the current implementation.

Given the possible unexpected results (e.g. above), though, I think it may still be better to notify the users somehow. Using `warnings` may be too 'noisy' here, perhaps an extra line or two in the docs? Is there a separate repository for the docs hosted on https://pyvcf.readthedocs.org?

Anyway, I'll do a rebase to undo the `__eq__` change, remove the new test file (re: the discussion on the pull request's page), and try to come up with another test to detect the pull request's bug in the future.