|
|
|
|
|
|
by lazerscience
4129 days ago
|
|
|
Maybe you can elaborate why this is supposed to be "broken by design"? Django's deprecation policy is one of the best, and also older versions receive (security) updates for a long time.
If you're not content with the functionality provided by an open source software there's still much room left to take actively part in its development. |
|
|
I tried and it was a complete waste of my time: https://code.djangoproject.com/ticket/18494
> Maybe you can elaborate why this is supposed to be "broken by design"?
Imagine the glibc fork() function changing its return value in the child process. The change is announced through an excellent deprecation policy that guarantees system wide breakage every month. Would that be acceptable?