#23469: django_1_6_0 compatibility check yields false posititves
--------------------------------------+------------------------------------
Reporter: brutasse | Owner: nobody
Type: Cleanup/optimization | Status: new
Component: Core (System checks) | Version: master
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
--------------------------------------+------------------------------------
Comment (by timgraham):
Duplicate of #21197, but I'd say we should be able to remove compatibility
checks after they've been in one or two versions of Django. We'd only need
to keep them around if we expect people will be skipping version of Django
when upgrading. I don't think we should really support/recommend that, but
I'm afraid it will happen frequently now that we've added LTS. Thoughts on
that?
--
Ticket URL: <https://code.djangoproject.com/ticket/23469#comment:2>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/066.3263d015f48d6b0ee2fb645aed810989%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
