Changes between Initial Version and Version 1 of Ticket #31301, comment 19
- Timestamp:
- Mar 4, 2020, 8:38:02 AM (5 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #31301, comment 19
initial v1 1 1 What's your suggested solution for users who are hitting this bug now? I can think of: 2 2 3 * Fork Django, backport the fix manually, and continue to maintain the fork until Django 3.1.0 is released 3 * Fork Django, backport the fix manually, and continue to maintain the fork until Django 3.1.0 is released and upgrading is viable 4 4 * Upgrade to Django development "master" branch, which sometimes breaks third-party Django addons 5 5 * Stop using Django until August 2020 rolls around (just sarcastic, sorry!)