

Initializes their self._paths in accordance to their given data. Meanwhile, LineCollection and PatchCollection This is also the case forĮllipseCollection. However, it appears that the supposedly empty collection object from Objects are already doing all it can to avoid doing transforms for empty _path.cpp would be nice, it appears that the collections and axes Ok, some more digging deepens the mystery. Make empty collections objects just avoid doing anything that So, do we want to make _path.cpp empty-friendly or should we just _path_module::affine_transform() which explicitly checks for anĮmpty vertices array and throws an exception if it is empty. > collections object more friendly to empty data.ĭigging further, it appears that the problem is in _path.cpp for

> matplotlib functions handle it gracefully, we should make the > that empty data is a perfectly valid scenario and given that > So, the question is, is this a bug or a feature? I > empty offsets, which leads to a failure in the affine > However, then we discover that polygon collection do not like > probably be done better by just using set_xmargin(0.05) and > min/max of the input data for the purpose of autoscaling > The immediate issue that comes up in scatter is that it > I have come across a little inconsistency that was unexpected On Tue, at 12:19 PM, Benjamin Root wrote: Meanwhile, LineCollection and PatchCollection initializes their self._paths in accordance to their given data. This is also the case for EllipseCollection. Its self._paths member contains a list of unit_circle() from Path. However, it appears that the supposedly empty collection object from scatter(, ) is not really empty. While an empty-friendly _path.cpp would be nice, it appears that the collections and axes objects are already doing all it can to avoid doing transforms for empty collections. So, do we want to make _path.cpp empty-friendly or should we just make empty collections objects just avoid doing anything that requires doing an affine transform? I agree a call with empty data should simply not plot anything.ĭigging further, it appears that the problem is in _path.cpp for _path_module::affine_transform() which explicitly checks for an empty vertices array and throws an exception if it is empty. Matplotlib functions handle it gracefully, we should make theĬollections object more friendly to empty data. That empty data is a perfectly valid scenario and given that other So, the question is, is this a bug or a feature? I personally believe However, then we discover that polygon collection do not like havingĮmpty offsets, which leads to a failure in the affine transformation. This can easily be bypassed with an if statement. Probably be done better by just using set_xmargin(0.05) and Min/max of the input data for the purpose of autoscaling (this can The immediate issue that comes up in scatter is that it attempts to find I have come across a little inconsistency that was unexpected in the
