You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Assuming that the RichHandler has become well-loved and accepted as the default logger, we should in all likelihood remove the ColorHandler provided in kedro.extras.logging. Possibly it's worth doing a quick bit of user research to check that no one feels strongly about keeping this in, but I'm pretty sure that no one really uses it and it will be redundant following the introduction of rich.
This is a breaking change - we need to add deprecation warnings in 0.18.x and then remove it in 0.19.
Note that when we have removed this and moved all extras.datasets out of kedro then all that will be left in kedro.extras is the ipython extension. Given that this namespace is probably changing to kedro.ipython, we will very nearly be at the point of being able to remove kedro.extras altogether 🥳
The text was updated successfully, but these errors were encountered:
Assuming that the RichHandler has become well-loved and accepted as the default logger, we should in all likelihood remove the
ColorHandler
provided in kedro.extras.logging. Possibly it's worth doing a quick bit of user research to check that no one feels strongly about keeping this in, but I'm pretty sure that no one really uses it and it will be redundant following the introduction of rich.This is a breaking change - we need to add deprecation warnings in 0.18.x and then remove it in 0.19.
Note that when we have removed this and moved all
extras.datasets
out of kedro then all that will be left inkedro.extras
is the ipython extension. Given that this namespace is probably changing tokedro.ipython
, we will very nearly be at the point of being able to removekedro.extras
altogether 🥳The text was updated successfully, but these errors were encountered: