> Backwards compatibility is the bigger concern here. I understand that, I believe there is always a way, because prior to 2008 when I switched to Django, I was commiter on a PHP library group that not only had the best code quality: but COMMITS to maintaining BC. Code that I have made prior to 2008 still works today with the last releases. Since then, I've been upgrading a lot of code, maintaining django packages with millions of downloads from Python 2 and Django 1 to nowadays and contribute the same to many libraries as much as I can, often proud to be the first to offer a patch, as such, I most definitely understand the cost of not maintaining BC.
I love BC, I think maintaining it is a challenge that always deserves as much time and effort as possible. But, since Django broke BC for on_delete, which I accept to be "for the greater good", I just wanted to at least discuss how this could be done to improve the results of security audits for all Django users, and not just me and my 20 yrs of pro xp, I'm too 1337 to need it for myself, I thought it was worth discussing about it for others. On a more emotional note, which I hope you will understand as **I've just been fired by one of the developers that I have admired most for more than a decade now, just for following OWASP recommandations**, no matter that I'm mentionning that my competitors do at least the same: THANK YOU Rene, For not completely discarding everything I offer for debate, it's been a while since django-developers make me feel like "just a craze", despite that I do actually maintain both governmental and financial websites in production which I develop and manage tech teams of, as part of different customers, and a lot of the money I make I actually throw away to other developers on R&D and other cool stuff which I wish I could be working on full time. To others: keep up the great work, Django is a fantastic project and I love it, last year I took a few months to assess all other more recent languages and frameworks I could find, with the purpose of deciding what my stack would be for the next decade and guess what: it's still Django ;) <3 -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/TrcSP2vCQe456Y-cKDkXK0HQMTiB-EsVd9ctmfkG5ZPDdqznDehSt8m-wjt6mHo51mAjoAk_9Kg5RcJrKDjBAqywkOpcfPDZ5aNFgtpsnKg%3D%40protonmail.com.
