On 15 September 2017 at 18:26, Adam Johnson <[email protected]> wrote: > (For some reason GMail is clipping your message before any content, I only > saw '... [Message clipped]' and had to click to see it all)
This must be due to using the Google Groups interface for posting - I'll stick to email from now on :-) On 15 September 2017 at 18:36, Tim Graham <[email protected]> wrote: > About the timing, it's too late to get this in to Django 2.0 as the > feature freeze is on Monday and I already have a large queue of review work > to do before then. I don't think it makes much difference since features > deprecated in both Django 2.0 and 2.1 will be removed in Django 3.0. > Ah ok - I didn't realise features deprecated in Django 2.0 and 2.1 would both be eligible for removal at the same time; re-reading the deprecation policy [1] I see now it's only Django 2.2 deprecations that would get deferred to Django 3.1. Given it sounds like this deprecation might be feasible, I've filed a ticket for doing so in Django 2.1: https://code.djangoproject.com/ticket/28606 And another for making ManifestStaticFilesStorage not leave the intermediate files behind: https://code.djangoproject.com/ticket/28604 Many thanks, Ed [1] https://docs.djangoproject.com/en/dev/internals/release-process/#internal-release-deprecation-policy -- 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 post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CAMtUAxvb2GSwCEztSgPKzatLj03HE%2BAXpcPTCjhY5-%3DiLXQK9A%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
