-
-
Notifications
You must be signed in to change notification settings - Fork 6.7k
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
When will Django4.2 be supported? #8942
Comments
the version was tested in CI, but not released yet. can you please try from master? |
Same question. I am already impatient to experience the new version. |
please don't be impatient! the new django release has some rough edges which is being ironed down. We might need to wait little bit more for a new DRF release |
OK, let me debug it carefully. Thanks! |
Hey @auvipy don't want to put any kind of pressure but could give some raw estimation on when we should expect DRF to support Django 4.2? |
I've updated Django from 4.1 to 4.2 in our project with DRF 3.14.0 and didn't noticed any issues so far. |
Are there any particular issues with Django 4.2 that you are aware of? I tried searching DRF issues and pull requests but could not find anything that seemed relevant. A cursory look at searching Django's bug tracker for "rest framework" also didn't turn up any relevant issues. |
Hi, i've encountered a problem after update django to 4.2:
And as I can see in official release notes (https://docs.djangoproject.com/en/4.2/releases/4.2/):
Will this be resolved in the latest version? |
This has already been fixed #8540 |
Thanks, my mistake. Reinstalling dependencies helped |
Anyone have an update as to when 4.2 might be officially be supported? |
can you guys please try DRF 3.14 with django 4.2.1 and report what is not working? when I added it to the CI nothing had to change TBH |
Hi, |
django 4.2 had some regressions which are already fixed |
When my newly created Django4.2 project imports DRF, the REST_FRAMEWORK configured in settings does not take effect
The text was updated successfully, but these errors were encountered: