Hi all,
>From my personal perspective, I'd love to have that feature in Django. It'd
make a significant difference especially for beginners learning Django, as
I know that during Django Girls workshop, teaching newcomers regex is one
of the most annoying and difficult parts of learning how Django works.
If there is anything I can do to help, I'm very interested. I'll try to
find some time today to review current pull requests and see if there is a
way for me to contribute.
Thanks to everyone who has worked on this so far!
Ola
On Tue, May 2, 2017 at 11:56 AM, Sjoerd Job Postmus <sjoerd...@sjec.nl>
wrote:
>
>
> On Tuesday, May 2, 2017 at 7:39:06 AM UTC+2, Emil Stenström wrote:
>>
>> I talked to Sjoerd separately. He is also very busy at the moment, but
>> was working on getting merge conflicts resolved soon. He will also post a
>> list of things that are still missing, but spontaneously thought that this
>> list would be short.
>>
>
> Just a quick list of things I think/know missing:
>
>
> - There are probably some simple converter implementations missing
> (FloatConverter, IntConverter, UUIDConverter, etc), and bikeshedding might
> need to happen on the exact implementation (what regex to use). Also, these
> could be added after the main logic is already completed.
> - The more complex part is (I think) figuring out how to deal with
> cases where we have a `path('/<something:int>', include(other_urls))` and
> `other_urls` also has a `path()` mentioning `something`. However this might
> just be my perfectionism and paranoia seeing edge-cases where there are
> none, or are sufficiently "edge" cases that we can suffice with a "just
> don't do it!".
> - Some positive yes/no on whether or not this is an actual desirable
> feature for Django from the core team.
> - Like I mentioned to Emil, I *think* this is "everything" that
> remains, but I might be missing a few things.
>
> Anyway, a careful review like Aymeric Augustin is suggesting might
> probably turn up a few more things that are missing.
>
> Emil: Thanks for pushing this forwards again, it got off the top of my
> mind, and it is good to have it back in focus again.
>
> --
> 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 post to this group, send email to django-developers@googlegroups.com.
> Visit this group at https://groups.google.com/group/django-developers.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/django-developers/c39a40a0-25b3-4a7b-b002-
> 767fadb38db7%40googlegroups.com
> <https://groups.google.com/d/msgid/django-developers/c39a40a0-25b3-4a7b-b002-767fadb38db7%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>
> For more options, visit https://groups.google.com/d/optout.
>
--
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 post to this group, send email to django-developers@googlegroups.com.
Visit this group at https://groups.google.com/group/django-developers.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-developers/CAFpnBuv4YFKG5qB%2BrGkZZG%2BfCcdk8zRj3XkLaDTcvkWCGLe1Qg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
