Re: Long-term direction for shortcuts

On Aug 2, 9:50 pm, Jacob Kaplan-Moss wrote: > On Sun, Aug 2, 2009 at 8:05 PM, Brent Hagany wrote: > > But, just to be explicit, I don't want to > > limit the discussion just to that patch, or to render_to_response or > > any particular shortcut.  

Re: Long-term direction for shortcuts

On Sun, Aug 2, 2009 at 8:05 PM, Brent Hagany wrote: > But, just to be explicit, I don't want to > limit the discussion just to that patch, or to render_to_response or > any particular shortcut.  First, we should discuss the larger issue of > whether technically unnecessary

Re: Long-term direction for shortcuts

On Aug 2, 9:14 pm, Malcolm Tredinnick 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

Re: Long-term direction for shortcuts

On Sun, 2009-08-02 at 18:53 -0700, chairface wrote: > On Aug 2, 8:36 pm, Malcolm Tredinnick > wrote: > > On Sun, 2009-08-02 at 18:05 -0700, Brent Hagany wrote: > > > > Putting too much weight on more or less throwaway comments in a single > > video isn't going to be

Re: Long-term direction for shortcuts

On Aug 2, 8:36 pm, Malcolm Tredinnick wrote: > On Sun, 2009-08-02 at 18:05 -0700, Brent Hagany wrote: > > Putting too much weight on more or less throwaway comments in a single > video isn't going to be particularly useful. They didn't seem to be "throwaway" to me -

Re: Long-term direction for shortcuts

On Sun, 2009-08-02 at 18:05 -0700, Brent Hagany wrote: [...] > If you watch the video, there was some disagreement with the idea > right from the start. Putting too much weight on more or less throwaway comments in a single video isn't going to be particularly useful. > The ticket that grew

Re: Long-term direction for shortcuts

Thanks Alex, I should have explicitly mentioned that rather than letting the video take care of it. I'm rather ambivalent on the common import location myself, but I am in very in favor of his stated reason for it: reducing the number of imports. I think good shortcuts can get us a lot of the

Re: Long-term direction for shortcuts

On Sun, Aug 2, 2009 at 8:05 PM, Brent Hagany wrote: > > Hello Django devs, > > The issue of making shortcuts better (and decreasing the number of > imports in views.py files) was brought up at DjangoCon, and now that > 1.1 is out the door, I would like to spark some

Long-term direction for shortcuts

Hello Django devs, The issue of making shortcuts better (and decreasing the number of imports in views.py files) was brought up at DjangoCon, and now that 1.1 is out the door, I would like to spark some discussion on what direction (if any) Django should take on the subject. (Relevant video

Re: Cache DB backend

On Sun, Aug 2, 2009 at 11:41 AM, Fraser Nevett wrote: [...] > I won't spend any time on refactoring, but I have opened a ticket > (#11623) and created a patch to ensure the table names get properly > quoted in the SQL (which I think is a good idea, even if actually > using the

Re: I need a pony: Model translations (aka "my proposal")

> I don't research your idea deeply but for first look it seems very > similar or same to django-multilingual. > http://code.google.com/p/django-multilingual/ >From the database perspective it is similar, meaning it uses the same database structure. What I tried to write down was mostly some

Re: Cache DB backend

On Aug 2, 2:48 pm, Russell Keith-Magee wrote: > On Sat, Aug 1, 2009 at 6:06 PM, Fraser  Nevett wrote: > > > I was looking at the database cache backend and noticed a number of of > > things that might be worth improving... > > >  * The

Re: Cache DB backend

On Sat, Aug 1, 2009 at 6:06 PM, Fraser Nevett wrote: > > I was looking at the database cache backend and noticed a number of of > things that might be worth improving... > >  * The "createcachetable" management command manually constructs and > executes SQL to create the