-
Notifications
You must be signed in to change notification settings - Fork 99
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
Use ArrayOrNone #350
Use ArrayOrNone #350
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry for being pedantic about the comments. I'm teaching this week. :)
Other than these comments and the test failure, LGTM.
chaco/tools/range_selection.py
Outdated
@@ -133,7 +133,7 @@ class RangeSelection(AbstractController): | |||
|
|||
# The data space start and end coordinates of the selected region, | |||
# expressed as a list. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This comment is out of date.
|
||
|
||
class TestArrayOrNone(unittest.TestCase): | ||
""" Test that the FutureWarning from numpy concerning comparison of arrays |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It would be helpful to expand upon this to include the numpy version where this is a warning and the version where it will become an exception.
The test failure is on python 3.4 using qt4. It appears to be due to a setup issue with pyside (perhaps this). I've not looked deeper into it. |
@cfarrow The remaining failures seem to be general problems with the Travis setup. |
Yes. The test failures look unrelated. We can deal with them elsewhere. |
LGTM |
Note that the last change to get this working with Enable's |
The next Chaco release will require an Enable release. I'm not too worried about that. Still LGTM |
Fixes all of the instances of
FutureWarning: comparison to `None` will result in an elementwise object comparison in the future.
that I could find.Additionally clean up a few warnings so that we have a clean test suite.