kill off getslice - #977
Conversation
…warnings fix numpy 1.20 DeprecationWarnings
…_volume Cache AllOutX volume
Codecov Report
@@ Coverage Diff @@
## dev-2.0 #977 +/- ##
===========================================
- Coverage 80.25% 80.01% -0.25%
===========================================
Files 136 136
Lines 14449 14445 -4
===========================================
- Hits 11596 11558 -38
- Misses 2853 2887 +34
Continue to review full report at Codecov.
|
|
@dwhswenson Do we want to keep python 2.7 support alive here (I don't have a python 2 environment anymore)? If so, feel free to close this PR |
|
Our official commitment is to support Py27 until |
|
@dwhswenson Github allows to change the base branch 😄 , so this should not be correct |
|
do you want me to properly rebase onto dev-2.0, or don't you mind pulling the master/dev-2.0 diffs as well? |
|
Doesn't matter. I've been doing the occasional merge of master into dev-2.0. If I've fallen a bit behind, no worries if your PR catches me up. As long as contributors get the appropriate credit (which (1) they would with this; (2) not an issue in this specific case) then I'm happy. |
dwhswenson
left a comment
There was a problem hiding this comment.
LGTM. There's a drop in coverage largely due to removing Py2.7 from the testing matrix (some code paths no longer used). I'll follow this up with a PR removing some of those code paths.
Related: note that part of the roadmap to 2.0 includes modifying trajectory so that it no longer inherits directly from list (instead wrapping a list and inheriting from collections.abc.Sequence).
As
list.__getslice__()has been deprecated since python2.0and killed since3.0this also removes theTrajectoryoverride of it.