TBH, I don't see a reason to create a precedent and deprecate it without any removal plans. Deprecation and removal is described in DEP 201, I don't think that we can revert [1] without a technical board approval 🤔 I would like to highlight that url() is an alias for re_path() so as far as I'm concerned migration is really straightforward and it's not time-consuming, you can use a short script to update all calls, e.g. [2], and you have 4 more years to do this.
Best, Mariusz [1] https://github.com/django/django/commit/2522559d1a612a4e8885de4780ff2b7aa7b8d375 [2] https://gist.github.com/felixxm/210e2a241c5ac17f5d2e569c31e1354c -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/cd5e03a7-697f-4665-b2a8-062f1181be8e%40googlegroups.com.
