Conversation
|
we have to decide when we will drop python 3.8 |
|
@auvipy I'd prefer it if issues like this linked cleanly to Python's deprecation timelines. |
I agree that's an ideal place we should aim for. If I'm realistic, though, we're not there yet. I think we should release bug fixes more often (perhaps on a monthly basis?) and align our feature releases (3.x) to be close to Django's. Dropping EOL Python versions can be done as soon as possible to be released the next time we bump the minor version (assuming we'll never bump the major again). |
carltongibson
left a comment
carltongibson
left a comment
There was a problem hiding this comment.
I think this should be merged now, assuming a new release to be v3.16.
|
@browniebroke @auvipy @tomchristie Anything else on your radar before a release? FWIW Django 5.0 will be EOL very shortly, and DRF does not yet officially declare support for Django 5.1 or 5.2. A release of current development branch (plus this PR, optionally) resolves that issue. |
I'm also in favour of doing this now |
browniebroke
left a comment
browniebroke
left a comment
There was a problem hiding this comment.
We should also update docs/index.md:
django-rest-framework/docs/index.md
Line 91 in 32dbd35
|
Updated in #9670 |
4 participants
After DRF 3.16 release is done, it might be right time to drop python 3.8 support... until then