Hello, I agree that different names would be better. I wouldn’t use the word “simple” since many “simple” things grow and become less simple in the long run. SOAP stands for Simple Object Access Protocol… For this reason url() and regex_url() have my preference.
I’m in favor of the <name:type> order because I believe that “consistency with Python” is a stronger argument than “consistency with Flask”, but I have to admit that I never made significant use of Flask. Best regards, -- Aymeric. > On 04 Oct 2016, at 00:11, Markus Holtermann <i...@markusholtermann.eu> wrote: > > Thanks for the draft, Tom. I'm a bit concerned that the different > `url*()` functions you can import will become confusing. Can we have > `regex_url()` (with chim for `url()`) -- as proposed -- and > `simple_url()` instead? > > /Markus > > On Mon, Oct 03, 2016 at 02:34:58PM -0700, Tom Christie wrote: >> Okay then, I've made some updates: >> >> * Updated the import design, in line with Jacob's suggestion. >> * Brief note on URL conventions, and the leading '/'. >> * Section on guarding against errors between `from django.conf.urls import >> url` and `from django.urls import url`. >> * Brief note on the internal RegexURLPattern API. >> * Breakout of required implementation tasks. >> >> Also, wrt Ryan's suggestion of reversing the ordering of name and type: >> I've some sympathy towards it, but I believe that presenting a consistent >> API between both Flask and Django is a more important factor. >> >> Cheers all, >> >> Tom >> >> -- >> 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/6a75cb7d-6df2-45e7-8efe-6c2f0526cfbe%40googlegroups.com. >> 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/20161003221128.GB23889%40pyler.local. > 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/DF8D81E2-7370-494C-90E4-E28E0A9B3897%40polytechnique.org. For more options, visit https://groups.google.com/d/optout.
