
discuss.python.org/t/_/85847/36
Preview meta tags from the discuss.python.org website.
Linked Hostnames
3Thumbnail

Search Engine Appearance
How can build backends avoid breaking users when they make backwards incompatible changes?
Given PEP 517 lots of projects now have their build backend defined like this: [build-system] requires = ["foo"] build-backend = "foo" This has lead to the following: When a new backend gets updated all users who bu…
Bing
How can build backends avoid breaking users when they make backwards incompatible changes?
Given PEP 517 lots of projects now have their build backend defined like this: [build-system] requires = ["foo"] build-backend = "foo" This has lead to the following: When a new backend gets updated all users who bu…
DuckDuckGo

How can build backends avoid breaking users when they make backwards incompatible changes?
Given PEP 517 lots of projects now have their build backend defined like this: [build-system] requires = ["foo"] build-backend = "foo" This has lead to the following: When a new backend gets updated all users who bu…
General Meta Tags
9- titleHow can build backends avoid breaking users when they make backwards incompatible changes? - #36 by abravalheri - Packaging - Discussions on Python.org
- charsetutf-8
- descriptionGiven PEP 517 lots of projects now have their build backend defined like this: [build-system] requires = ["foo"] build-backend = "foo" This has lead to the following: When a new backend gets updated all users who bu…
- generatorDiscourse 3.5.0.beta9-dev - https://github.com/discourse/discourse version 63328ede0859c0bbe35b7492b630c27201b59711
- theme-color#fff
Open Graph Meta Tags
9- og:site_nameDiscussions on Python.org
- og:typewebsite
- og:imagehttps://us1.discourse-cdn.com/flex002/uploads/python1/original/1X/f93ff97c4f381b5e8add5a0c163b4ded29f20ed7.png
- og:urlhttps://discuss.python.org/t/how-can-build-backends-avoid-breaking-users-when-they-make-backwards-incompatible-changes/85847/36
- og:titleHow can build backends avoid breaking users when they make backwards incompatible changes?
Twitter Meta Tags
5- twitter:cardsummary
- twitter:imagehttps://us1.discourse-cdn.com/flex002/uploads/python1/original/1X/f93ff97c4f381b5e8add5a0c163b4ded29f20ed7.png
- twitter:urlhttps://discuss.python.org/t/how-can-build-backends-avoid-breaking-users-when-they-make-backwards-incompatible-changes/85847/36
- twitter:titleHow can build backends avoid breaking users when they make backwards incompatible changes?
- twitter:descriptionTo be honest, I believe that the following would be very very useful and would be a tremendous quality of life improvement: Not hiding warnings. This is a well-know and recuring topic of discussion. The snippet in Warnings in backends as suppressed by frontends · Issue #558 · pypa/packaging-problems · GitHub looks like an interesting starting point [1]. It would also be incredible useful in other contexts (e.g. setuptools/setuptools/command/editable_wheel.py at v78.1.0 · pypa/setuptools · G...
Item Prop Meta Tags
12- position1
- headlineHow can build backends avoid breaking users when they make backwards incompatible changes?
- datePublished2025-03-25T03:12:10Z
- articleSectionPackaging
- keywords
Link Tags
37- alternate nofollowhttps://discuss.python.org/t/how-can-build-backends-avoid-breaking-users-when-they-make-backwards-incompatible-changes/85847.rss
- apple-touch-iconhttps://us1.discourse-cdn.com/flex002/uploads/python1/optimized/1X/4c06143de7870c35963b818b15b395092a434991_2_180x180.png
- canonicalhttps://discuss.python.org/t/how-can-build-backends-avoid-breaking-users-when-they-make-backwards-incompatible-changes/85847?page=2
- iconhttps://us1.discourse-cdn.com/flex002/uploads/python1/optimized/1X/9997f0605d56c4bfecd63594f52f42cdafd6b06a_2_32x32.png
- urlhttps://discuss.python.org/u/notatallshaw
Links
12- https://discuss.python.org
- https://discuss.python.org/c/packaging/14
- https://discuss.python.org/categories
- https://discuss.python.org/guidelines
- https://discuss.python.org/privacy