cyclic import dependency when extend builtin backend

[yi.codeplayer@…]

When writing a custom cache backend which inherit from django's builtin memcache backend, say mycache.py:

    from django.core.cache.backends.memcached import CacheClass as BaseCacheClass
    class MyCache(BaseCacheClass):
        ....

and set backend to "mycache.MyCache" in settings.py, then mycache.py and django.core.cache.__init__.py import each other.
Turn django.core.cache.__init__.py::cache object to be a SimpleLazyObject would solve this problem.

[Russell Keith-Magee]

Can't reproduce -- I dropped a custom cache class defined as you describe, and don't the problem you describe. Looking at the code, I can't even work out what set of conditions would allow this to be reproduced -- I don't see any circular dependency. memcached doesn't import anything from the django.core.cache.

[anonymous]

You need to config this custom backend to the default cache backend in settings.py to reproduce this problem, django.core.cache would import the default cache backend.
sorry for poor english description.

[Russell Keith-Magee]

And that's exactly what I did. If you want to convince me, you'll need to provide a sample project.

[anonymous]

I was wrong, there's no bug in django ;-)