Peter Cock
Peter Cock
https://github.com/jamescasbon/PyVCF/blob/master/docs/HISTORY.rst lists changes in v0.6.7 (21 Feb 2014), but not v0.6.8 (18 March 2016), nor any of the as-yet unreleased changes since. Cross reference https://pypi.org/project/PyVCF/#history and #302 - a more...
The latest git tag is ``v0.6.0`` and is missing ``v0.6.1`` though ``v0.6.8`` as listed on https://pypi.org/project/PyVCF/#history
On all the releases to date, including 0.6.8, the README is treated as plain text on PyPI: https://pypi.org/project/PyVCF/0.6.8/ This is likely because it fails validation as a standalone RST file...
The first bullet list was wrongly preceded by a double colon meaning it was rendered as a literal block. Separately all the bullet lists were needlessly indented, which on GitHub...
### Checklist - [X] I added a descriptive title - [X] I searched open reports and couldn't find a duplicate ### What happened? Attempting to add a (Windows only) patch...
Noted in passing on #2507, ``` $ python test_SCOP_online.py test_search (__main__.ScopSearch) Test search. ... ERROR ====================================================================== ERROR: test_search (__main__.ScopSearch) Test search. ---------------------------------------------------------------------- Traceback (most recent call last): File "test_SCOP_online.py", line...
Currently this sometimes causes a CI failure, and isn't doing anything useful due to changes on the CodeCov side. Closes #3752 - but I would like to see this functionality...
Noted today while parsing mtDNA GenBank files from NCBI: BiopythonParserWarning: Structured comment not parsed for NC_037500. Is it malformed? BiopythonParserWarning: Structured comment not parsed for NC_037499. Is it malformed? BiopythonParserWarning:...
See e.g. https://help.github.com/articles/open-source-licensing/ Traditionally (unless opting for the GNU GPL) use a file named LICENSE, LICENSE.txt or LICENSE.md etc if using a markup language, and put put the name of...
Quoting the main README, > # Mac OS X > Currently no support is given for iOS. If anyone is interested in getting this to work feel free to contact...