Personally I think that the current name does a fairly good job of conveying the effect, and this is coming from someone who doesn’t explicitly understand the internal process and is merely inferring it.
However my anecdote doesn’t negate what we all see around the internet, so I suppose it can be improved. I am a strong -1 on adding words like “dangerously” to the method name. I feel that method names are not the place for warnings like that. I do not like the precedent that it sets for other potentially unsafe methods within the Django codebase, and i believe that it’d result in unnecessarily verbose project code. Kye Russell Sent from my iPhone > On 19 Feb 2020, at 5:11 pm, Adam Johnson <m...@adamj.eu> wrote: > -- 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/ECEDF3F5-2245-4FEA-850E-54FDC43A7891%40kye.id.au.
