On Mon, Oct 20, 2008 at 9:01 AM, David Huard <[EMAIL PROTECTED]> wrote:
> I would oppose any change to histogram calling convention that does not > fix a critical bug. I agree that using a built-in name as an argument is > a bug, but I believe it is the lesser evil compared to asking users to > change their code > again. I think in this case we have to change it, but we can do it gently. Ie, for a release cycle, if we detect "range" in the kwarg case, we'll set the correct kwarg, eg "binrange", issue a warning, but not raise an error. That way users can fairly easily change their code w/o breakage. Whoever does the deprecation should note the date and version of the deprecation warning, so we will know when enough time and releases have passed to remove range entirely. JDH ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Matplotlib-devel mailing list Matplotlib-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
