Opened 3 weeks ago

Closed 8 days ago

Last modified 8 days ago

#37293 closed Cleanup/optimization (fixed)

Update warnings for new release cycle (DEP 20)

Reported by: Carlton Gibson Owned by: Carlton Gibson
Component: Utilities Version: dev
Severity: Normal Keywords:
Cc: Triage Stage: Ready for checkin
Has patch: yes Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no

Description

Warnings existing for Django 7.0 and 7.1, which will be Django 2028 and 2029. Add new classes for these, and remove uses of the old one, leaving as compatibility aliases. Update usages, and docs as appropriate.

Change History (10)

comment:1 by Carlton Gibson, 3 weeks ago

​PR

comment:2 by Carlton Gibson, 3 weeks ago

Has patch: set

comment:3 by Sarah Boyce, 3 weeks ago

Triage Stage: Unreviewed → Accepted

comment:4 by Jacob Walls, 8 days ago

Triage Stage: Accepted → Ready for checkin

comment:5 by nessita <124304+nessita@…>, 8 days ago

In 0d0e7f1:

Refs #37293 -- Aliased RemovedInDjango70Warning to RemovedInDjango2028Warning.

Updated references to RemovedInDjango70Warning to use the new warning,
and adjusted references to "Django 7.0" to "Django 2028".

RemovedInDjango70Warning remains importable as an alias of the same
class, so existing warning filters and except clauses in third-party
code keep working across the rename.

comment:6 by nessita <124304+nessita@…>, 8 days ago

Resolution: → fixed
Status: assigned → closed

In 52abe52:

Fixed #37293 -- Renamed RemovedInDjango71Warning to RemovedInDjango2029Warning.

Per DEP 20, Django's version numbers are calendar-based from 2028, so
deprecation warning classes are now named after the calendar version
that removes the feature they mark, and the deprecation timeline is
headed by the same calendar version.

Updated references to RemovedInDjango71Warning to use the new warning,
and adjusted references to "Django 7.1" to "Django 2029".

comment:7 by nessita <124304+nessita@…>, 8 days ago

In 026b005:

Refs #37293 -- Updated deprecation docs for calendar-based warning names.

comment:8 by Natalia <124304+nessita@…>, 8 days ago

In b6cb9c6:

[6.1.x] Refs #37293 -- Aliased RemovedInDjango70Warning to RemovedInDjango2028Warning.

Updated references to RemovedInDjango70Warning to use the new warning,
and adjusted references to "Django 7.0" to "Django 2028".

RemovedInDjango70Warning remains importable as an alias of the same
class, so existing warning filters and except clauses in third-party
code keep working across the rename.

Backport of 0d0e7f15038360c158b6d22c679b47b21557fa1f from main.

comment:9 by Natalia <124304+nessita@…>, 8 days ago

In 1fc6109d:

[6.1.x] Refs #37293 -- Updated deprecation docs for calendar-based warning names.

Backport of 026b005f3dc43a98557ce5a546b5e4938d06fed1 from main.

comment:10 by Natalia <124304+nessita@…>, 8 days ago

In 8e0e994:

[6.0.x] Refs #37293 -- Aliased RemovedInDjango70Warning to RemovedInDjango2028Warning.

Updated references to RemovedInDjango70Warning to use the new warning,
and adjusted references to "Django 7.0" to "Django 2028".

RemovedInDjango70Warning remains importable as an alias of the same
class, so existing warning filters and except clauses in third-party
code keep working across the rename.

Backport of 0d0e7f15038360c158b6d22c679b47b21557fa1f from main.

Note: See TracTickets for help on using tickets.
Back to Top