Re: [Django] #14761: URL resolving / reversing design doesn't allow alternate specs

[Django]

#14761: URL resolving / reversing design doesn't allow alternate specs
-------------------------------------+------------------------------------
Reporter: samuel337 | Owner: knbk
Type: New feature | Status: assigned
Component: Core (URLs) | Version: master
Severity: Normal | Resolution:
Keywords: url resolve reverse | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+------------------------------------
Changes (by knbk):

* status: new => assigned
* cc: marten.knbk@… (added)
* needs_better_patch: 1 => 0
* needs_tests: 1 => 0
* owner: nobody => knbk
* has_patch: 1 => 0

Comment:

I'll address this as part of https://groups.google.com/forum/#!topic
/django-developers/WQoJN_MGTOg.

--
Ticket URL: <https://code.djangoproject.com/ticket/14761#comment:6>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

[Django]

#14761: URL resolving / reversing design doesn't allow alternate specs

-------------------------------------+-------------------------------------
Reporter: samuel337 | Owner: Marten
| Kenbeek

Type: New feature | Status: assigned

Component: Core (URLs) | Version: dev

Severity: Normal | Resolution:
Keywords: url resolve reverse | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0

-------------------------------------+-------------------------------------

Comment (by Tom Carrick):

I'm not sure how much need for this ticket there is now that we have path
converters?

--
Ticket URL: <https://code.djangoproject.com/ticket/14761#comment:7>

[Django]

#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>