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
Some deprecations in cudf are issuing a FutureWarning that is intended to match pandas behavior. These deprecations are not safe to remove until some (potentially future) pandas removal. This deviates from the current Developer Guide, which says:
cuDF follows the policy of deprecating code for one release prior to removal. For example, if we decide to remove an API during the 22.08 release cycle, it will be marked as deprecated in the 22.08 release and removed in the 22.10 release.
We should annotate any warnings that are meant to be kept with a code comment like # Do not remove until pandas removes this. so that developers can differentiate deprecated code paths that are safe to remove from those that are expected to be maintained.
We should also update the developer guide with this new guidance with a policy for pandas API deprecations that we have to preserve.
The text was updated successfully, but these errors were encountered:
Some deprecations in cudf are issuing a
FutureWarning
that is intended to match pandas behavior. These deprecations are not safe to remove until some (potentially future) pandas removal. This deviates from the current Developer Guide, which says:We should annotate any warnings that are meant to be kept with a code comment like
# Do not remove until pandas removes this.
so that developers can differentiate deprecated code paths that are safe to remove from those that are expected to be maintained.We should also update the developer guide with this new guidance with a policy for pandas API deprecations that we have to preserve.
The text was updated successfully, but these errors were encountered: