You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Ensure all pysam code is 64bit clean to match new htslib API
Adopt new region parser
Avoid need to vendor htslib
Work with htslib team to remove few remaining abort()s in the library code
Work with htslib team to provide noninvasive output/warning/error hooks
Integrate htslib logging with Python logging
Provide a cleaner and more consistent API
Complete deprecation of older APIs
Harmonize various HtsFile subclasses
Deprecate legacy VCF parser
Support new VCF features
Follow progress in hts-specs (VCF 4.4), htslib
URL encoded info and format values (needed to escape VCF delimiters in values)
Improve Python developer/user experience
Prevent virtually all crashes/segfaults from Python wrapper
Fully control C struct lifetimes (we're close, I think)
Hide all memory management details
Support efficient header translation without user intervention to hide
translation details from one file/header to another. Currently users
need to know about TIDs, etc.)
Prevent or catch and recover from illegal operations
Provide on high quality comprehensive documentation -- a historical weakness
Poor/incomplete documentation has been the biggest weakness of pysam
historically.
Modernize test suite
modernize current test suite
add more high code coverage unit tests
add lightweight system tests
Simplify scope by wrapping only htslib, not samtools or bcftools
Subject to debate of course. I don't use this functionality, so it
isn't important to me. This becomes a much easier feature to support
if a developer who cares greatly about this feature steps up to work on
this.
The text was updated successfully, but these errors were encountered:
Kevin's vision for pysam2
translation details from one file/header to another. Currently users
need to know about TIDs, etc.)
historically.
isn't important to me. This becomes a much easier feature to support
if a developer who cares greatly about this feature steps up to work on
this.
The text was updated successfully, but these errors were encountered: