# Revision history [back]

When the name of a function or a method changes, there is a one-year deprecation warning (meaning that during at least one year, when you use an old method, you will get a warning pointing yo to the new one), but there is no long-term centralized tool.

Your suggestion of keeping suc a long-term "dictionary" of such evolutions is a very good idea however.

When the name of a function or a method changes, there is a one-year deprecation warning (meaning that during at least one year, when you use an old method, you will get a warning pointing yo to the new one), but there is no long-term centralized tool.

Your suggestion of keeping suc such a long-term "dictionary" of such evolutions is a very good idea however.

When the name of a function or a method changes, there is a one-year deprecation warning (meaning that during at least one year, when you use an old method, you will get a warning pointing yo to the new one), but there is no long-term centralized tool.

Your suggestion of keeping such a long-term "dictionary" of such evolutions is a very good idea however.

EDIT Regarding books, it is possible to add the code that belongs to the book in the doctests of Sage so that changes are detected and the book can be updated, see the \$SAGE_LOCAL/src/sage/tests.