Re:Removing Python 2.x support from Django for version 2.0
by imtringued on Thursday January 19, 2017 @09:24AM
(#13435953)
Mark it as deprecated, change the documentation to tell the user to use the new function Y instead and the most important part: keep the old api even if it's crufty. Wait for a few years until everyone upgraded and no longer uses any deprecated functions. Maybe make a final LTS release for those who don't want to upgrade. Then and only then should you ever break backwards compatibility.
[ Parent
| on HN ]
Re:Removing Python 2.x support from Django for version 2.0
by ubernostrum on Thursday January 19, 2017 @03:08PM
(#13439044)
Wait for a few years until everyone upgraded and no longer uses any deprecated functions.
Then view HN threads of people saying they have thirty-million-line codebases which utterly rely on deprecated functionality and they never ever plan to upgrade or do even basic maintenance ever for any reason ever, and will abandon your platform and completely rewrite in something that treats them "better".