Percentile Clipping causes FutureWarning #1713

Activity

1. matthewdouglas commented on Jul 21, 2025

   

   matthewdouglas

   on Jul 21, 2025

   Member

   More actions

   Thanks for the feedback!

   Yes, percentile clipping itself is deprecated. We could make this more clear with a warning in the optimizers. Setting block_wise=False is a similar situation where we have marked a function it uses as deprecated in bitsandbytes.functional but it may be more clear if we warned when initializing an optimizer with it.
2. matthewdouglas

   added

   DocumentationImprovements or additions to documentationImprovements or additions to documentation

   Contributions WelcomeWe welcome contributions to fix this issue!We welcome contributions to fix this issue!

   OptimizersIssues or feature requests relating to optimizersIssues or feature requests relating to optimizers

   on Jul 21, 2025
3. matthewdouglas

   modified the milestones: v0.46.2This milestone has been deleted, v0.47.0 on Jul 21, 2025
4. matthewdouglas

   modified the milestones: v0.47.0, v0.48.0 on Aug 11, 2025
5. matthewdouglas

   modified the milestones: v0.48.0, v0.49.0 on Sep 29, 2025
6. matthewdouglas

   modified the milestones: v0.49.0, v0.50.0 on Dec 11, 2025
7. matthewdouglas

   linked a pull request that will close this issueRemove deprecated APIs: research module, non-blockwise optimizers, and legacy quantization functions #1871on Feb 20, 2026
8. TimDettmers commented on Feb 21, 2026

   

   TimDettmers

   on Feb 21, 2026

   Collaborator

   More actions

   Closing this as resolved. As matthewdouglas confirmed, percentile clipping is deprecated, which is why the underlying function triggers a FutureWarning. This is by design. A clearer deprecation warning at optimizer initialization time would improve the UX, but the behavior is intentional.
9. TimDettmers

   closed this as completedon Feb 21, 2026