On Aug 2, 9:14 pm, Malcolm Tredinnick <malc...@pointy-stick.com> wrote:
> Simon has not justified why his particular preference for imports > necessarily meets even the common case and why he, or somebody else, > cannot put their own choices for common imports into a single that they > import (pretty normal "reduce repetition" pattern in Python). This is true. This discussion is a chance for Simon or someone who agrees with him to justify their position. You are begging the question. > It's a source for ideas for further discussion with more details. A > conference Q&A session lacks a *lot* of details. Again, this discussion is a quest for more details. > They are considered on a case-by-case basis, just like all proposed > changes. This isn't new policy and I'm sure why it needs to be changed. This is true as far as it goes, but it is not the whole story. I am certainly not asking for a change in policy. This list discusses a lot of things that have no code behind them yet, particularly in the area of what features should be implemented. This is the kind of discussion I am asking for. Is the feature of an expanded shortcuts module worthwhile, and consistent with Django's goals? I have seen indications that opinion is split, and this is the place to discuss such things. > In the case of your proposed changes to render_to_response(), I see some > added complexity that impacts everybody (maintainers, documentation > readers and devs) for a small target userbase to do something that > already only takes a single line (and if counting the imports really > adds to your line count by a significant percentage, the code is so > small that it's a tough push uphill to argue it's a common use-case -- > you import once and reuse often). It is my contention that the added complexity is negligible such that the word "complexity" does not even fit the situation. But this is the type of discussion that belongs in the ticket. It's actually a discussion we've already had. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
