2012/10/2 Olivier Grisel <[email protected]>: > I am +1 for renaming params to the `n_things` scheme as long as we can > implement the DeprecationWarning with explicit version numbers in the > message ("parameter x is deprecated in version y and will be renamed > in version y + 2; use param n_things instead").
BTW, if 2 releases ~ 6months is too short we can increase to 4 releases instead. I have +1 for this when deprecation handling is a simple argument renaming. For more complex deprecation logics that are harder to maintain we can probably stay to 2 releases. The point is that we need to have explicit deprecation error message and log those changes in the whatsnew file as usual. -- Olivier http://twitter.com/ogrisel - http://github.com/ogrisel ------------------------------------------------------------------------------ Don't let slow site performance ruin your business. Deploy New Relic APM Deploy New Relic app performance management and know exactly what is happening inside your Ruby, Python, PHP, Java, and .NET app Try New Relic at no cost today and get our sweet Data Nerd shirt too! http://p.sf.net/sfu/newrelic-dev2dev _______________________________________________ Scikit-learn-general mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/scikit-learn-general
