Thanks for your reference. I'm not using any custom fields defined by myself. Probably they are from one of the used apps.
Thanks! Gabriel On 6 mar., 15:25, Łukasz Rekucki <lreku...@gmail.com> wrote: > On 6 March 2011 13:55, Gabriel - Iulian Dumbrava > > <gabriel.dumbr...@gmail.com> wrote: > > I couldn't find any reference on what I have to change to get rid of > > this deprecation warning. I'm using the trunk version: > > > VERSION = (1, 3, 0, 'beta', 1) > > > This is what I get: > > > [Sun Mar 06 14:47:36 2011] [error] /usr/local/lib/python2.6/dist- > > packages/django/db/models/fields/subclassing.py:80: > > DeprecationWarning: A Field class whose get_db_prep_value method > > hasn't been updated to take `connection` and `prepared` arguments. > > [Sun Mar 06 14:47:36 2011] [error] new_class = super(SubfieldBase, > > cls).__new__(cls, name, bases, attrs) > > http://docs.djangoproject.com/en/dev/releases/1.2/#get-db-prep-method... > > All deprecated things start with PendingDeprecationWarning (which is > silent by default), so if you're seeing a DeprecationWarning it's most > likely something deprecated in previous version. > > (Unless you're using Python 2.7 or later, which also silences > DeprecationWarning, so you should run your code with "-Wd" to see > them). > > -- > Łukasz Rekucki -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
