Cache backend API should close()

[Russell Keith-Magee]

At present, only the memcached cache backends have a close() method. This means that you can't reliably call close() on a cache -- you need to protect it with "hasattr(cache, 'close')".

Django's own code even does this, in the end-request signal handler.

The cache backend API should include a no-op close() method by default, matching the API from the memcached backend.

The close() method (and the end-request handler) were added in r8418

[mgrouchy]

I added a pull request for this issue here: ​https://github.com/django/django/pull/218

I'm not sure if there any extra test requirements for this, but if there are, I would appreciate some guidance there and will update the pull request appropriately.

[Russell Keith-Magee]

Thanks for the patch!

The test requirement here is really just to exercise the new API point. There is an existing suite of cache tests in regressiontests/cache that use every function on the cache API; add a new test that calls close to the BaseCacheTest, and that method will be invoked for every cache backend.

[mgrouchy]

Replying to russellm:

Thanks for the patch!

No Problem!

The test requirement here is really just to exercise the new API point. There is an existing suite of cache tests in regressiontests/cache that use every function on the cache API; add a new test that calls close to the BaseCacheTest, and that method will be invoked for every cache backend.

I added a Test, basically ensuring close exists and then using the endpoint.

Let me know if anything needs to be changed there. Pull request has been updated.

[mgrouchy]

Hey, is there anything that I should do to get this ticket closed/pull request merged?

[Russell Keith-Magee]

Nope - the patch looks good to commit. Thanks!

[Aymeric Augustin]

In 4c5cea70734fe8f4082c6a9bd8b26cf0a157ca78:

Merge pull request #218 from mgrouchy/ticket_18582

Fixed #18582 -- Added a no-op close to BaseCache