#31534 closed Cleanup/optimization (fixed)
Deprecate django.conf.urls.url().
| Reported by: | David Smith | Owned by: | David Smith |
|---|---|---|---|
| Component: | Core (URLs) | Version: | dev |
| Severity: | Normal | Keywords: | |
| Cc: | Triage Stage: | Accepted | |
| Has patch: | yes | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
The docs for django.conf.urls.url say:
This function is an alias to django.urls.re_path(). It’s likely to be deprecated in a future release.
It looks like the change was made in this commit back in 2016 (Django 2.0). Given some years have passed, is it now the time to deprecate this function?
Change History (7)
comment:1 by , 5 years ago
| Component: | Uncategorized → Core (URLs) |
|---|---|
| Summary: | Depreciate django.conf.urls.url → Deprecate django.conf.urls.url(). |
| Triage Stage: | Unreviewed → Accepted |
| Type: | Uncategorized → Cleanup/optimization |
| Version: | 3.0 → master |
comment:2 by , 5 years ago
| Owner: | changed from to |
|---|---|
| Status: | new → assigned |
Note:
See TracTickets
for help on using tickets.
Agreed. We can deprecate it in Django 3.1 and remove in Django 4.0. Aymeric proposed to deprecate it in Django 3.1 when we discussed DEP 201.