Skip to content
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

broken_barh does not properly support units #4906

Merged
merged 2 commits into from Aug 14, 2015

Conversation

jrevans
Copy link

@jrevans jrevans commented Aug 11, 2015

broken_barh and hist were not handling unitized data.

This addresses an issue in #4897.

@@ -2275,6 +2275,11 @@ def broken_barh(self, xranges, yrange, **kwargs):

.. plot:: mpl_examples/pylab_examples/broken_barh.py
"""
# process the unit information
self._process_unit_info(xdata=xranges[0], ydata=yrange[0], kwargs=kwargs)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This line is too long, could you please wrap it?

@tacaswell tacaswell modified the milestone: next point release Aug 12, 2015
@WeatherGod
Copy link
Member

Just restarted one of the Travis jobs (it is a known intermittent error due to Travis).

Things look good here. It just would be nice to have a test to catch these things in the future. Not sure how to do that without adding dependencies, though. @dopplershift , do you have any suggestions on that?

@dopplershift
Copy link
Contributor

Well, there's a "mini" unit library in the unit examples. All of my own testing to date relies upon pint, which I don't think we want to depend upon.

tacaswell added a commit that referenced this pull request Aug 14, 2015
FIX: broken_barh does not properly support units
@tacaswell tacaswell merged commit 0e3a6ae into matplotlib:master Aug 14, 2015
@jrevans jrevans deleted the issue05 branch August 17, 2015 17:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants