I feel like we open a can of worms if we go down this road. Where do we draw the line between what we do and don't mention regarding *Python* optimization? The Django docs don't need to layout the current state of the Python ecosystem IMO. I don't doubt the info is helpful, but I don't think Django's docs is the right place for it. There are many Python web frameworks out there, should every framework mention this type of stuff in their docs? It seems like a duplication of effort.
(summary of what I said in IRC) On Friday, September 13, 2013 1:41:43 PM UTC-4, Daniele Procida wrote: > > On Fri, Sep 13, 2013, Florian Apolloner <f.apo...@gmail.com <javascript:>> > wrote: > > >On Friday, September 13, 2013 4:18:05 PM UTC+2, Daniele Procida wrote: > >> > >> Any further comments would be welcomed. There's some disagreement about > >> the appropriateness of the last section, < > >> https://github.com/django/django/pull/1463/files#L5R318> so it would > be > >> particularly usefukl to have some further opinion on that. > >> > > > >Personally I'd remove it completely for the following reasons: > > * Especially newcomers tend to think that they need the most performant > >system > ) > > * This dual-import of libraries where you try to select the most > >"efficient" versions quite often results in issues for those versions > which > >didn't get used by the developer > > I've re-written that section now to emphasise the caveats and the need to > verify improvements, and to de-emphasise the prospect of exciting > perfromance gains. > > Daniele > > -- You received this message because you are subscribed to the Google Groups "Django developers" 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 http://groups.google.com/group/django-developers. For more options, visit https://groups.google.com/groups/opt_out.
