ImproperlyConfigured on Django 1.3 about django-pyodbc HOT 4 CLOSED

@dlo I found that the error occurs by importing the module query.py that defines the custom query class, though it doesn't appear on the traceback. I remember that the custom query class feature is supported only on Django 1.1 or older and it is never used on Django 1.2 or newer. So we will be able to fix the bug simply by removing the module from the repo and dropping support for these old versions of Django from the backend.

I don't think we need to support those legacy versions of Django anymore because they are too old to use for people and it makes the codes complicated. I will fix the bug by removing the module if you agree with that. What do you think of that?

from django-pyodbc.

I agree...1.6 will be coming out soon anyways, and support for two versions back is more than enough.

We should just update the README to let people know, but otherwise I think this is totally ok.

from django-pyodbc.

Thank you for your reply. Okay, from here on I will make further changes that might incompatible with Django 1.1 or earlier.

from django-pyodbc.

Fixed.

from django-pyodbc.