Metadata-Version: 1.1
Name: vcfpy
Version: 0.2.1
Summary: Python 3 VCF parser to circumvent problems in PyVCF
Home-page: https://github.com/bihealth/vcfpy
Author: Manuel Holtgrewe
Author-email: manuel.holtgrewe@bihealth.de
License: MIT license
Description: =====
        VCFPy
        =====
        
        
        .. image:: https://img.shields.io/pypi/v/vcfpy.svg
                :target: https://pypi.python.org/pypi/vcfpy
        
        .. image:: https://img.shields.io/travis/bihealth/vcfpy.svg
                :target: https://travis-ci.org/bihealth/vcfpy
        
        .. image:: https://readthedocs.org/projects/vcfpy/badge/?version=latest
                :target: https://vcfpy.readthedocs.io/en/latest/?badge=latest
                :alt: Documentation Status
        
        .. image:: https://pyup.io/repos/github/bihealth/vcfpy/shield.svg
             :target: https://pyup.io/repos/github/bihealth/vcfpy/
             :alt: Updates
        
        
        Python 3 VCF parser that allows both reading and writing
        
        * Free software: MIT license
        * Documentation: https://vcfpy.readthedocs.io.
        
        Why another VCF parser for Python!
        ----------------------------------
        
        I've been using PyVCF with quite some success in the past.
        However, the main bottleneck of PyVCF is when you want to modify the per-sample genotype information.
        There are some issues in the tracker of PyVCF but none of them can really be considered solved.
        I tried several hours to solve these problems within PyVCF but this never got far or towards a complete rewrite...
        
        For this reason, VCFPy was born and here it is!
        
        What's the State?
        -----------------
        
        VCFPy is the result of two full days of development plus some maintenance work later now (right now).
        I'm using it in several projects but it is not as battle-tested as PyVCF.
        
        Why Python 3 Only?
        ------------------
        
        As I'm only using Python 3 code, I see no advantage in carrying around support for legacy Python 2 and maintaining it.
        At a later point when VCFPy is known to be stable, Python 2 support might be added if someone contributes a pull request.
        
        =======
        History
        =======
        
        0.2.0 (2016-09-19)
        ------------------
        
        * First release on PyPI.
        
Keywords: vcfpy
Platform: UNKNOWN
Classifier: Development Status :: 2 - Pre-Alpha
Classifier: Intended Audience :: Developers
Classifier: License :: OSI Approved :: MIT License
Classifier: Natural Language :: English
Classifier: Programming Language :: Python :: 3
Classifier: Programming Language :: Python :: 3.3
Classifier: Programming Language :: Python :: 3.4
Classifier: Programming Language :: Python :: 3.5
