--
Ticket URL: <https://code.djangoproject.com/ticket/32490>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
Comment (by Tilman Koschnick):
[https://github.com/django/django/pull/14060 PR]
--
Ticket URL: <https://code.djangoproject.com/ticket/32490#comment:1>
* status: new => closed
* resolution: => wontfix
Comment:
I'm not sure why this needs to be defined in Django itself. The
[https://docs.djangoproject.com/en/stable/topics/http/urls/#path-
converters default set of path converters] doesn't even contain base64
which would seem to be more useful than base36 to me. Creating
[https://docs.djangoproject.com/en/3.1/topics/http/urls/#registering-
custom-path-converters custom path converters] is trivial, so I'm not sure
that we need to expand the default set. If you disagree, please feel free
to raise this on the DevelopersMailingList.
--
Ticket URL: <https://code.djangoproject.com/ticket/32490#comment:2>
Comment (by Tilman Koschnick):
Hi, is lack of complexity reason not to add something? The other
converters are trivial as well, after all.
Just for the record: base64 is less suitable for my use case; while it is
somewhat shorter than base36, it adds capital letters, "=" and (in the url
safe variant) "-" and "_" into the mix, so doesn't fulfil my "easier to
type" criterion.
--
Ticket URL: <https://code.djangoproject.com/ticket/32490#comment:3>
Comment (by Mariusz Felisiak):
> Hi, is lack of complexity reason not to add something?
No, it's not. We cannot add hundreds of features just because they are not
complex (''"death by a thousand cuts"'').
--
Ticket URL: <https://code.djangoproject.com/ticket/32490#comment:4>
Comment (by Tilman Koschnick):
Okay, understood, thanks for clarifying!
--
Ticket URL: <https://code.djangoproject.com/ticket/32490#comment:5>