-
-
Notifications
You must be signed in to change notification settings - Fork 282
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Django 1.5.5 produces error #36
Comments
Are you sure? A downgrade to Django 1.5.4 did not remove the error for me, and this project's tests pass with Django 1.5.5. Here is more info: The error occurs at https://github.com/ui/django-rq/blob/master/django_rq/queues.py#L68 where there is a comment
But I am not: I am using |
I realize that the
It is from the Django debug toolbar. @Koed00 are you also using the debug toolbar? |
@kennknowles Yes, using |
The problem seems to be that debug-toolbar monkey patches I'm closing this issue because the is a bug in |
It is not a bug in The "bug" is that Anyhow, it is built in to the design decision to leverage the cache framework (how else are you going to get a redis client out of the cache implementation other than looking at its internals?) so the only obvious solution is to remove this. If you feel it is worth tracking, I suggest opening a new ticket for the design bug. |
It's true that Instead of always subclassing I haven't had the time to test this out or think too deeply about this though, but I still think the monkey patching is the cause of the problem ;). Thoughts? |
Well, as long as we are looking at basically private members of
In the short term, you can also remove the cache stats from the debug panel, something like so:
|
FYI, I just tested the latest master branch using |
Django 1.5.5. produces this error with django-rq
AttributeError: 'CacheStatTracker' object has no attribute '_client'
When I downgrade to 1.5.4 , all is well. Been having problems with 1.5.5 and many other packages. I think some 1.6 code snuck into the 1.5.5 security update.
The text was updated successfully, but these errors were encountered: