> To be clear, "pressure to get the API right on the first shot" is a > statement of fact about adding APIs to a heavily used project in > general, not a comment on anything said in this mailing thread. Just > that in this case there's a lot of ways to get the ergonomics wrong.
Yes and I think thats also a good reason to "bake smaller buns" (german saying), and not trying to revamp too many things in one go. So how about doing this iteratively - fixing the DB url thing first (as there is prior art to learn from), and in a second step trying to deal with the cache settings?
Cheers, Jörg -- 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/cf7661f1-cdf9-87cb-10fb-a58e1ed25edb%40netzkolchose.de.
