test numpydoc 1.1.0

[carlosp420]

• I hereby agree to dual licence this and any previous contributions under both
  the Biopython License Agreement AND the BSD 3-Clause License.

• I have read the CONTRIBUTING.rst file, have run flake8 locally, and
  understand that AppVeyor and TravisCI will be used to confirm the Biopython unit
  tests and style checks pass with these changes.

• I have added my name to the alphabetical contributors listings in the files
  NEWS.rst and CONTRIB.rst as part of this pull request, am listed
  already, or do not wish to be listed. (This acknowledgement is optional.)

[peterjc]

P.S. Have you seen #3024 which is why I downgraded numpydoc to avoid v1.1.0, cross reference the numpydoc issue and PR?

[carlosp420]

P.S. Have you seen #3024 which is why I downgraded numpydoc to avoid v1.1.0, cross reference the numpydoc issue and PR?

yes. I wanted to fix the issue and it appears that numpydoc v1.1.0 does not crash when the mocking for Bio.Restriction.Restriction is removed. Ie the travis builds passed.

[peterjc]

Oh. That's probably good, but how long does it make the autogenerated output - and is the order stable (i.e. sorted)?

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 83.88%. Comparing base (c4bb6d9) to head (4a8b50d).
Report is 1734 commits behind head on master.

Additional details and impacted files

@@           Coverage Diff           @@
##           master    #3045   +/-   ##
=======================================
  Coverage   83.88%   83.88%           
=======================================
  Files         321      321           
  Lines       51941    51941           
=======================================
  Hits        43572    43572           
  Misses       8369     8369           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[carlosp420]

Oh. That's probably good, but how long does it make the autogenerated output - and is the order stable (i.e. sorted)?

I just noticed that the output is huge! it is documenting all the entries in Restriction_Dictionary and the output is not sorted. Multiple builds of the docs result in different sorting of the documented entries of the dictionary.
Maybe that is why this module was ignored in autodoc_mock_imports ?

Then maybe I will wait until your PR in numpydoc gets resolved to clean up this draft pull request.

[peterjc]

Yes, that was why I'd excluded the restriction docstrings - it was rather unmanageable.

The other tweaks (typos and formatting) are worth applying now, but let's see what the numpydoc decide to do.

[peterjc]

I didn't trace back when we moved off numpydoc 1.0.0 but we've been on numpydoc==1.7.0 for a few months now. I believe all the other minor fixes here (typos etc) have now been applied to the master branch - thank you!