Brute force Checklist. #38

vincentdavis opened this Issue Apr 20, 2016 · 2 comments


None yet

3 participants


As suggested by Markus Piotrowski

  1. Title
  1. Is the text up-to-date? (Python versions etc)
  2. Formatting
  3. Suggestion: Python/Biopython commands, keywords, module/function names should be formatted as inline-code with single backticks, e.g. Bio.SeqIO ??? Or bold???
  4. If applicable, they can also serve as links to the respective Wiki page
  5. Code output and command-line examples should be formatted as block code with three backticks instead of several single line inline-code statements.
  6. Check block code for trailing white spaces, which may result in the addition of an (unnecessary) horizontal scrollbars as here:
  7. Code
  8. Code should be checked for a minimum of PEP8 compliance.
  9. The code should work (as it is) under Biopython 1.66
  10. Since we are recommending Python 3.5 as environment, the code should work under Python 3.5 ???
  11. Links
  12. Check all links
  13. 'Repair' broken links
    Try to find a link that's more likely to be stable. E.g. for papers I think that references (or Pubmed references) are more stable than linking to a special page of the respective journal or private or institutional homepages. With you can do a reverse doi lookup for a given paper.
  14. Links with anchors (.../some_page#jump_here) may have issues with upper/lowercase formatting (#13)
  15. Are the links up-to-date? E.g. in the Python Quick Reference links to Python 2.5
  16. References
  17. Some pages used a PubMed plugin under MediaWiki to display references (#12). Since it's unlikely (?) to have a functional replacement, I would suggest to convert them to simple links.
  18. RSS feeds
  19. As above, embedding an existing RSS feed seems hard (#4), again I would suggest replace with a link pointing to the RSS feed
peterjc commented Apr 21, 2016

Yes, as with the main Tutorial and docstrings, try to make code examples work on both Python 2 and 3 (using simple print functions with one variable). If not easy, I think it is time to prefer Python 3 syntax but perhaps the example should not this explicit for the lingering Python 2 users.

@peterjc peterjc added the help wanted label May 2, 2016
MarkusPiotrowski commented May 2, 2016 edited

Internal links with anchors: See also #13

The correct format for anchored links in the Wiki pages is "all lower case with hyphens",

Each heading has such an anchor, so you can easily jump/link to any heading you like.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment