RemovedInDjango18Warning in Django 1.7

[epicserve]

When running my tests I'm getting.

RemovedInDjango18Warning: 'The `cycle` template tag is changing to escape its arguments;
the non-autoescaping version is deprecated. Load it from the `future` tag library to start
using the new behavior.

[tim-schilling]

The debug toolbar needs to support Django 1.4 and up. Because of that, it's using the old definition of the cycle template tag.

@aaugustin Do you know if there is a reason why the {% load cycle from future %} wasn't backported to Django 1.4 and 1.5? Otherwise when 1.8 comes out we'll have to write our own template tag to account for this while we continue to support 1.4 and 1.5. You mentioned that as a solution in #546.

[epicserve]

Why doesn't DjDt follow Django's support cycle? Django 1.5 is no longer support. If someone is still using something older than Django 1.6 they could just use an older release of DjDt.

[tim-schilling]

Django 1.4 is supported until at least March 2015 according to the docs.

[epicserve]

I'm confused then ... why is this at the top of the Django 1.5 docs?

[tim-schilling]

You're right, 1.5 is no longer supported by Django, but 1.4 is a long term support release.

[epicserve]

Have I entered some sort of Django circular support paradox? Anyway, my 2 cents ... DjDt should just create a new release that supports Django 1.7 and Django 1.6 and anyone that needs Django 1.5 or lower could just use an older version of DjDt. It would be a lot simpler for DjDt to support. Plus anyone that's using Django 1.5 or lower isn't the type of person that is going to want or need the latest and greatest from DjDt.

[epicserve]

In the mean time ... can anyone tell me why this doesn't work for ignoring the warning?

import warnings
from django.utils.deprecation import RemovedInDjango18Warning
warnings.simplefilter('ignore', RemovedInDjango18Warning)

[aaugustin]

That "solution" would be fairly bad for every Django 1.4 user who hasn't pinned their dev dependencies.

[epicserve]

@aaugustin, so you make a decision on what to support by developers bad practices?

[aaugustin]

@epicserve Yes, I care about all users, even those who aren't aware of all best practices.

[epicserve]

@aaugustin I care about all users as well. That's why I try to educate and help users instead being an enabler for bad practices.

[aaugustin]

I checked the source code:

• {% load cycle from future %} is never used
• {% cycle 'djDebugOdd' 'djDebugEven' %} is the only use of the cycle tag

Since it's only called on fixed strings, escaping has no effect and we don't need to make any changes for Django 1.8. There's a spurious warning on 1.7 but it will go away on 1.8.

Making our own version of the cycle tag or breaking 1.4 seem more inconvenient than having a warning, so my suggestion is not to do anything.