Re: r11964 and PendingDeprecationWarning

2010-01-04 Thread Luke Plant
On Tuesday 05 January 2010 00:40:42 Jannis Leidel wrote: > Maby just an odd idea but what happens if someone monkey patched > them as lists (e.g. because the input formats weren't configurable > until now)? Would lazy() handle this automatically given list and > tuples are both iterables or sho

Re: r11964 and PendingDeprecationWarning

2010-01-04 Thread Jannis Leidel
Hi Luke, > pinging Jannis - did you see this? Can you have a look at my > suggestion? Mea culpa, this is indeed an issue and I like your solution of using lazy(), since the *_INPUT_FORMATS tuples are only used for iteration. Maby just an odd idea but what happens if someone monkey patched the

Re: r11964 and PendingDeprecationWarning

2010-01-04 Thread Luke Plant
pinging Jannis - did you see this? Can you have a look at my suggestion? Cheers, Luke -- "Love is like an hourglass, with the heart filling up as the brain empties." Luke Plant || http://lukeplant.me.uk/ -- You received this message because you are subscribed to the Google Groups "Django

r11964 and PendingDeprecationWarning

2009-12-28 Thread Luke Plant
Hi all, Since changeset 11964 (i18n improvements), if you import django.forms.fields (directly or indirectly), you get a PendingDeprecationWarning. This is a problem, because it means that Django's own code is emitting a warning. It's especially a problem if you use a line like this: impor