#14761: URL resolving / reversing design doesn't allow alternate specs
-------------------------------------+-------------------------------------
Reporter: samuel337 | Owner: Marten
| Kenbeek
Type: New feature | Status: closed
Component: Core (URLs) | Version: dev
Severity: Normal | Resolution: needsinfo
Keywords: url resolve reverse | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Mariusz Felisiak):
* status: assigned => closed
* resolution: => needsinfo
* stage: Accepted => Unreviewed
Comment:
Replying to [comment:7 Tom Carrick]:
> I'm not sure how much need for this ticket there is now that we have
path converters?
That's true. Resolving URLs is not the same as it was 8 years ago,
`RegexURLResolver` doesn't exist anymore, we have path converters etc.
This ticket should be redefined if any changes still need to be made
--
Ticket URL: <https://code.djangoproject.com/ticket/14761#comment:8>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/0107018b22e95878-f4b95d6b-e438-4d16-9cac-487d9fbd2118-000000%40eu-central-1.amazonses.com.
