Join GitHub today
GitHub is home to over 20 million developers working together to host and review code, manage projects, and build software together.
Remove explicit children invalidation in update_position method #6692
Conversation
mdboom
added the
needs_review
label
Jul 5, 2016
tacaswell
and 1 other
commented on an outdated diff
Jul 5, 2016
| @@ -446,15 +446,8 @@ def _get_gridline(self): | ||
| return l | ||
| - def update_position(self, loc): | ||
| - 'Set the location of tick in data coords with scalar *loc*' | ||
| - x = loc | ||
| - | ||
| - nonlinear = (hasattr(self.axes, 'yaxis') and | ||
| - self.axes.yaxis.get_scale() != 'linear' or | ||
| - hasattr(self.axes, 'xaxis') and | ||
| - self.axes.xaxis.get_scale() != 'linear') | ||
| - | ||
| + def update_position(self, x): |
tacaswell
Owner
|
tacaswell
added this to the
2.1 (next point release)
milestone
Jul 5, 2016
|
appveyor failure is connectivity to anaconda.org issue |
|
I will make a performance test then, but the test suit runs the same amount of time with this change. And as I have mentioned in the commit message |
|
I suspect that (given the age) it was using some internal details that have moved under it. Don't worry about adding a performance test (unless @mdboom disagrees). I think this is otherwise |
Kojoley commentedJul 5, 2016
This invalidation actually does nothing as the
Line2Ddoes not have nor use the_invalidfield. There are_invalidxand_invalidyfields for this purpose, but them are private members. Moreover, theset_xdataandset_ydatamethods internally invalidate the state (what is more reasonablethen an external invalidation).