Hmmm. I have to say I think there are areas where we could get a better ROI on our time than this.
I always took the capitalisation of GET &co to come from HTTP <https://tools.ietf.org/html/rfc2616#page-36> — I'd say that's where PHP took it from too but 🤷♀️ That they're a bit "unpythonic" (Meh™) is OK: they serve to remind that request was ultimately mapped from an HTTP request, and most of that is still available if you care to dig. <form method=GET ...> Then request.form_data -> Oh, where's my form data, if not in "form_data"? Well it's in "query_params"... Hmmm That's no better learning experience. Folks still have to learn how HTTP maps to request properties. > ... better ROI... There's lots we might take from DRF. The one that's come up before, and which for work was began, but only began, was content negotiation. I'd rather see work/energy/effort spent there. Maybe we'd have different names if we began today. But this would be very disruptive. We've just had a discussion re url() suggesting that "deprecated but not really" is an error on our part, and having two ways to do things definitely isn't "pythonic". So I'm inclined towards the range between -1 and -0 — but I haven't had my coffee yet. 😝 Kind Regards, Carlton > -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/bc60e809-6390-44fc-a07a-ed6e0f9eef86%40googlegroups.com.
