-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Minor changes to Seq integer multiplication methods and tests for inplace addition methods #1735
Conversation
Codecov Report
@@ Coverage Diff @@
## master #1735 +/- ##
=========================================
- Coverage 85.57% 85.17% -0.4%
=========================================
Files 331 331
Lines 50086 50086
=========================================
- Hits 42859 42660 -199
- Misses 7227 7426 +199
Continue to review full report at Codecov.
|
Including the class name in the exception is a nice improvement in case of subclasses. Likewise the extra tests seems sensible too. The TravisCI failures seem unrelated, Python 2.7.14,
and Python 3.5,
My guess is the release of ReportLab 3.5.0 earlier this week is to blame, see https://pypi.org/project/reportlab/#history In this case the TravisCI weekly cron job will test the master branch in a few days - and I expect that to fail. After confirming that, your changes look good to merge. Do you want to add yourself to the |
Thank you Peter, yes, I added myself to |
This pull request relates to pull request #1669 and corresponding issue #1659 where we introduced integer multiplication methods for Seq-like objects, I propose 2 small changes.
Seq
,UnknownSeq
, andMutableSeq
multiplication methods when subclassing, here is an example:Seq
,UnknownSeq
, andMutableSeq
addition methods. These+=
operations are available even though the__iadd__
methods are never defined, so I thought they should be tested.I'd be grateful for review of the changes, any thoughts?
One related point,
__imul__
methods are defined but__iadd__
methods are not. Does this matter? Probably we should ideally be consistent, but it is likely inconsequential?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 and understand that AppVeyor andTravisCI will be used to confirm the Biopython unit tests and
flake8
stylechecks pass with these changes.
I have added my name to the alphabetical contributors listings in the files
NEWS.rst
andCONTRIB.rst
as part of this pull request, am listedalready, or do not wish to be listed. (This acknowledgement is optional.)