-
Notifications
You must be signed in to change notification settings - Fork 439
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
Incompatibility with latest DRF 3.12.0 #641
Comments
Hi, I also noticed this problem about 1 hour ago as 3.12.0 DRF was released. Currently I had to use fixed requirement of DRF 3.11.1 Let me add some logs to make better search engine inexing ;)
|
Patched with #642 |
@axnsan12, could we get your attention here? |
Having same issue here after updating to 3.12.1, (running with django 3.1.2 on Ubuntu).
|
same here @OmenApps |
same problem than @OmenApps |
do update on drf, for me decided |
I'm worried this project is no longer maintained given that there has been no activity since February (#590). The maintainer, @axnsan12, is still slightly active on GitHub (see https://github.com/rabbitmq/rabbitmq-management/issues/836#issue-678646238 dated Aug 13), but there hasn't been any activity on this repo. Does the project need to be forked? |
We can continue on my fork, drf-yasg2. Would someone like to volunteer to fix the test suite and build failures? |
Thanks! Here are some PR's I triaged that would be good to migrate over:
Typos: Perhaps we should comment on the PRs when they've been merged into the fork so that if people need the fix, they know to check out |
This comment has been minimized.
This comment has been minimized.
@johnthagen Issues now enabled |
Hi. |
Same problem here. Sad to see this package dying... |
Since the maintainers of this repo are not replying, we've moved to my fork drf-yasg2 |
I wrote an email to the owner of this repository stating the problems, I hope he has a solution. |
Please note a compatible and stable version of this package is now available on pypi; drf-yasg2 |
See [thread](axnsan12/drf-yasg#641)
See [thread](axnsan12/drf-yasg#641)
Uninstalling drf-yasg & then installing drf_yasg2 fixed this for me |
Probably means I should move some of my patches over to |
The libary we use currently for this `drf-yasg` appears to be no longer maintained and we are experiencing an error, having upgraded to a newer version of `djangorestframework`, see: axnsan12/drf-yasg#641 I also had to update to the latest version of `pytest` as I consistently got an error installing dependencies. IssueID #35
The previously referenced django-heluser branch was merged to the master branch and we pin the latest commit in master branch as time of writing. We need to pin specific versions of djangoresetframework and ipython because: - drf-yasg is not compatible with DRF 3.12+, see details: axnsan12/drf-yasg#641 - ipython 7.17+ requires python 3.7+ (we need to support Python 3.6) Refs: LIIK-197
The previously referenced django-heluser branch was merged to the master branch and we pin the latest commit in master branch as time of writing. We need to pin specific versions of djangoresetframework and ipython because: - drf-yasg is not compatible with DRF 3.12+, see details: axnsan12/drf-yasg#641 - ipython 7.17+ requires python 3.7+ (we need to support Python 3.6) Refs: LIIK-197
The previously referenced django-heluser branch was merged to the master branch and we pin the latest commit in master branch as time of writing. We need to pin specific versions of djangoresetframework and ipython because: - drf-yasg is not compatible with DRF 3.12+, see details: axnsan12/drf-yasg#641 - ipython 7.17+ requires python 3.7+ (we need to support Python 3.6) Refs: LIIK-197
The previously referenced django-heluser branch was merged to the master branch and we pin the latest commit in master branch as time of writing. We need to pin specific versions of djangoresetframework and ipython because: - drf-yasg is not compatible with DRF 3.12+, see details: axnsan12/drf-yasg#641 - ipython 7.17+ requires python 3.7+ (we need to support Python 3.6) Refs: LIIK-197
@JoelLefkowitz I was thinking to update the description of the issue, to move to Even I have been already moved to |
@fasih I went ahead and created a new issue with a clear title about the fork. I think it's good to keep this issue open to document the clear DRF 3.12 problem for current users of |
1.20.0 is now out with the fix. I think we can consider this closed. |
Encode has just released the new version of DRF
django-rest-framework 3.12.0
which has dropped all compat support to Django < 2 urlsAffected import in dry-yasg
DRF merged PR
DRF Commit
The text was updated successfully, but these errors were encountered: