-
-
Notifications
You must be signed in to change notification settings - Fork 6.9k
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
Version 3.14.0 proposal #8599
Version 3.14.0 proposal #8599
Conversation
Good stuff, thanks Tim. I'd like #7522 to be part of this too, but would be great to get a review onto that from someone other than myself. |
Co-authored-by: Adam Johnson <[email protected]>
@tomchristie can we release this? It's blocking upgrades to Django 4.1 |
Consideration... I suppose we might want to include #8617 for this release. Thoughts? We also ought to add a https://www.django-rest-framework.org/community/3.14-announcement/ page to the docs. |
@tomchristie it would be nice to not delay too much the release of this version since it's actually blocking everyone from upgrading to Django 4.1 |
I can add the community page this weekend. If #8617 isn't resolved by then, perhaps that goes in a 3.15 release when it does get merged? |
I believe #8617 is now in a mergeable state. Should be able to make it in to the 3.14 release. |
This deprecation was never released in the 3.13.x series and therefore can't be removed at the same time the replacement is released.
I've added a draft for the community page, including the mention for #7522. I also noticed that the warnings for One thing that I caught was that the openapi |
class RemovedInDRF314Warning(PendingDeprecationWarning): | ||
pass |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this and the above RemovedInDRF313Warning
can be removed? I cannot find any other references.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I kept it as per the comments in #8589.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That argument doesn't really convince me, DRF has never kept around the old warning classes for previous versions, e.g. RemovedInDRF312Warning
was removed in d45e000. Similarly, Django does not keep around old warning classes "just in case".
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd rather leave that decision up to a maintainer. I wasn't a part of the original discussion so it'd be disingenuous for me to say that by convincing me, the past argument is moot.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry to have missed this thread!
I was assuming that RemovedInDRF313Warning
would be deleted with the 3.14 release.
(My point was only that deleting an exception class in a minor release would constitute a breaking change)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
CC @adamchainz - put out a PR to delete the now-unused warnings: #8664
|
||
Our requirements are now: | ||
|
||
* Python 3.6+ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
imho this should be 3.7+ but we need #8518 to be merged
* Python 3.6+ | |
* Python 3.7+ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd be happy merging that but I'll defer to @tomchristie.
Our requirements are now: | ||
|
||
* Python 3.6+ | ||
* Django 4.1, 4.0, 3.2, 3.1, 2.2 (LTS) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
* Django 4.1, 4.0, 3.2, 3.1, 2.2 (LTS) | |
* Django 4.1, 4.0, 3.2 (LTS) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I can do the related clean ups in a separate PR as well.
Hello friends, do we have a timeline on when will the new release be released? I think this should be prioritized because DRF can't be used with Django 4.1 because of the Thank you and kind regards, |
Also, are you working on a specific branch or tag for the 3.14 release ? I'd be happy to install it directly from github using the Thanks again |
It's right at the top of the list. Ought to be this week. |
Arrrgggh. Don't be too mean. |
Tom, what about the comments from the reviews? There were some good points
that we were looking for your opinion on.
…On Wed, Sep 21, 2022, 8:08 AM Tom Christie ***@***.***> wrote:
Merged #8599 <#8599>
into master.
—
Reply to this email directly, view it on GitHub
<#8599 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAJYZP2PQUZWAEOT34XDZK3V7MCEVANCNFSM56E5GBCQ>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
I see the follow-up PR now and that you're on it! Thank you. |
Okay... I'm ready for us to release this tomorrow unless there's any objections? I've updated the release date in the docs to 22nd Sept 2022. |
@tomchristie is DRF's policy regarding |
I responded in-thread, but also noting here: The pattern in past releases has been to drop the old unused exception classes - I think we should do the same for 3.14. Would be best to not repeat the same strangeness with DRF 3.14. 😄 (Sorry for not being clear on my original PR) |
It looks like Django 2.2 is being dropped, but the setup.cfg still looks like it allows for Django 2.2 both in the https://github.com/encode/django-rest-framework/blob/master/setup.py#L85 I also would think dropping Django 2.2 should be added to the release notes. |
Okay, released. |
Thanks for the release. 🙏️ |
Wonderful. Thank you ❤️ |
* Version 3.14.0 * Update docs/community/release-notes.md to use proper links. Co-authored-by: Adam Johnson <[email protected]> * Add community announcement page for version 3.14 * Remove deprecated NullBooleanField. * Change openapi _get_reference removal to 3.15 This deprecation was never released in the 3.13.x series and therefore can't be removed at the same time the replacement is released. * Removing deprecated openapi methods. Co-authored-by: Adam Johnson <[email protected]>
Currently projects using Django 4.1 are blocked from using Django Rest Framework due to #8591. Since that was merged, I think a release is warranted.
I started putting together the changes from 3.13.1, and discovered there were a couple of API changes. I suspect this should require a minor version change, but a maintainer should make that final call.
If the version change isn't desired, let me know and I can remove that.