From: Eric Firing [mailto:efiring@…229…]
Sent: Wednesday, October 06, 2010 20:53I modified it slightly and applied to the maintenance branch. It will
get merged into the trunk eventually.Your patch as submitted was not respecting the previously-set value of
self._tight, hence my modification.
Thank you for the review and correction, Eric. Your modification clarified
for me another behavior of the prior and new implementations: The argument
tight=True is retained for future autoscaling calls with tight=None, but
tight=False doesn't stick; future calls use the automatic children-based
logic. Does the Axes._tight attribute need to have three legal values
(corresponding to tight, loose, and children-based) to yield the documented
behavior?