Urllib3 v2.6.0 recently removed several deprecated APIs that had been problematic since 2019. Even though these APIs had been marked as deprecated in the documentation since 2022 and emitted DeprecationWarnings for over three years, many users were caught off guard by the removal, which broke dependent libraries. The recommended alternative APIs do not have compatibility issues between urllib3 versions 1.x and 2.x, yet the warnings failed to prompt timely action from users and library maintainers. The author concludes that the current DeprecationWarning system is ineffective for alerting Python developers about API changes. Despite being an easy-to-use feature of the language, the warnings are often ignored by default, limiting their impact. Suggestions for improvement include creating a custom deprecation warning class to ensure visibility or adopting a versioning system like SemVer, which would allow for major version changes without advance notice. The author seeks other ideas on how to effectively handle deprecations, emphasizing the challenge of ensuring that developers stay informed.