-
Notifications
You must be signed in to change notification settings - Fork 51
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
Using with Django 1.11 - audiofield middleware is no longer compatible #27
Comments
Thanks for opening an issue on this, personally I haven't tested Django 1.11 |
Have been playing around with this (still no luck) - for reference the full traceback is:
I've tried rewriting the ThreadLocal class as 1.11/1.10 compatible per the docs in several different ways but it always spits out the same 'TypeError' on them. Example of rewrite attempt:
I've got some other things that I'd like to try but I'm a little stumped by I'm sure that I'm just not understanding how it's used in this case though - if it's not an imposition, would you be able to point me at any reading that might clarify it? The wsgi docs haven't been terribly clear on the thread request usage but, I also don't have much experience in this area. |
I have rewritten the middleware and addressed the issue - my initial inability to address the issue was due to my having kept audiofield inside the Updating the middleware location to Class now written as:
|
Pull #28 submitted to address this - some small work needed to make it back compatible with pre-1.10 versions, testing needs to be done as well. |
While attempting to install this on my project (which is using Django 1.11) it throws the error
TypeError: object() takes no parameters
becauseMIDDLEWARE_CLASSES
has been deprecated and replaced withMIDDLEWARE
.I attempted the resolution in the docs, updating the audiofield.middleware.threadlocals module as follows.
Prev:
Updated:
However, this does not solve the issue and the error
TypeError: object() takes no parameters
is still thrown.I will keep looking into this and submit a pull if I am able to find a solution but please advise if there is a known resolution for this issue.
Thanks!
The text was updated successfully, but these errors were encountered: