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
Import error - Django 3.0.1 - ImportError: cannot import name 'available_attrs' from 'django.utils.decorators' #280
Comments
I believe that this is due to the fact the pypi repo is not properly updated. The tar and whl files still contain the bugs fixed in #276 |
Any Idea, when the pypi repo will be update with a new release? |
will push a new pypi release soon |
@auvipy Any issue you see as a must to be fixed before release? |
check your email |
@auvipy Can this issue be closed? |
Yes. I think this is resolved in the updated version.
From: Brian Helba <notifications@github.com>
Sent: August 20, 2020 8:45 AM
To: chibisov/drf-extensions <drf-extensions@noreply.github.com>
Cc: Sulantha Sanjeewa <sulantha@enigmabiomedicalgroup.com>; Author <author@noreply.github.com>
Subject: Re: [chibisov/drf-extensions] Import error - Django 3.0.1 - ImportError: cannot import name 'available_attrs' from 'django.utils.decorators' (#280)
@auvipy<https://github.com/auvipy> Can this issue be closed?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub<#280 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AOCETI5KRJ75DN5AZJG2HOTSBVAGBANCNFSM4KAEPS7Q>.
|
thanks |
I still face the same issue from drf_yasg.views import get_schema_view
File ".venv/lib/python3.7/site-packages/drf_yasg/views.py", line 5, in <module>
from django.utils.decorators import available_attrs
ImportError: cannot import name 'available_attrs' from 'django.utils.decorators' |
File "/app/.heroku/python/lib/python3.9/site-packages/drf_yasg/views.py", line 5, in |
not related to this package |
Hi, I am using drf-extensions 0.5.0 with Django 3.0.1 and Python 3.7.
However, when I try to use the package, I get this error. I believe this has something to do with compatibility if Django 3.0.
Is this an easy fix?
The text was updated successfully, but these errors were encountered: