# How can build backends avoid breaking users when they make backwards incompatible changes?

**URL:** <https://discuss.python.org/t/how-can-build-backends-avoid-breaking-users-when-they-make-backwards-incompatible-changes/85847>\
**Category:** Packaging\
**Created:** [March 25, 2025, 3:12am UTC](https://discuss.python.org/t/how-can-build-backends-avoid-breaking-users-when-they-make-backwards-incompatible-changes/85847 "2025-03-25T03:12:10Z")\
**Posts on this page:** 1\
**Showing post:** 62

<div class="post-metadata">

**Author:** ![notatallshaw](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/notatallshaw/32/10861_2.png) [@notatallshaw](https://discuss.python.org/u/notatallshaw)\
**Post date:** [November 2, 2026, 10:15pm UTC](https://discuss.python.org/t/how-can-build-backends-avoid-breaking-users-when-they-make-backwards-incompatible-changes/85847/62 "2026-11-02T22:15:59Z")

</div>

Update on this, pyproject-hooks now forwards build warnings, and pip logs them by default when building local sources: [Announcement: pip 26.3 release!](https://discuss.python.org/t/announcement-pip-26-3-release/109822)

---

_[View the full topic](https://discuss.python.org/t/how-can-build-backends-avoid-breaking-users-when-they-make-backwards-incompatible-changes/85847)._