﻿id	summary	reporter	owner	description	type	status	component	version	severity	resolution	keywords	cc	stage	has_patch	needs_docs	needs_tests	needs_better_patch	easy	ui_ux
28663	Check for likely incorrectly migrated django.urls.path() calls (that still have regex characters in the route)	Chris Lamb	nobody	"I recently moved a project to Django 2.x, including moving to ``django.urls.path``. However, I wasn't careful enough in the details so ended up migrating, for example:

{{{#!python
    from django.conf.urls import url

    url('^faq$', views.faq,
        name='faq'),
}}}

to

{{{#!python
    from django.urls import path

    path('^faq$', views.faq,
         name='faq'),
}}}

This doesn't cause any errors (!) but results in, for example, {{{reverse('faq')}}} returning the (encoded) url {{{/%5Efaq$}}}.

As this is a) likely to be very common during the migration with a high cost of a true positive, combined with b) the fact that the chance of a false positive is fairly low, I suggest we add a check for this.

(PR incoming...)"	New feature	closed	Core (URLs)	2.0	Normal	fixed	check urls		Accepted	1	0	0	0	0	0
