On 12/5/06, Adrian Holovaty <[EMAIL PROTECTED]> wrote:
> It's an abstraction of the workflow "Display an HTML form, force a
> preview, then do something with the submission."
Very slick.
> What other sorts of things can we make abstractions for,
> given a Form?
I wanted to come up with a standa
On 11/11/05, Jacob Kaplan-Moss <[EMAIL PROTECTED]> wrote:
>
> On Nov 11, 2005, at 1:54 PM, pbx wrote:
> > Actually, Ian's idea was part of my original thinking as well -- if
> > you
> > make "__exact" optional, you can completely remove "pk" (which is
> > itself a weird exception to the keyword ru
I like it, but I also wish that "__exact" was optional, so I might not
be a good person to ask...
ian
On 11/11/05, Adrian Holovaty <[EMAIL PROTECTED]> wrote:
>
> On 11/9/05, pbx <[EMAIL PROTECTED]> wrote:
> > In short, the proposal is: Single non-keyword arguments to get_object()
> > should be a
OK, now I feel even dumber than I originally did...
So, why does Django need it, if it comes for free with WSGI?
-ian
On 11/7/05, Adrian Holovaty <[EMAIL PROTECTED]> wrote:
>
> On 11/7/05, Ian Maurer <[EMAIL PROTECTED]> wrote:
> > Excuse my ignorance, but I am trying
Excuse my ignorance, but I am trying to learn more about WSGI and how
it fits in with these Python frameworks
Could we use this stuff, without additional work, if Django was
WSGI-compliant? Isn't that the "dream" of WSGI as a way of creating
framework-neutral middleware? If this is so what is
On 10/17/05, Ian Maurer <[EMAIL PROTECTED]> wrote:
> One thing I really like about the URL mapping/dispatch functionality
> of Django is the ability to bring in an existing app and put it in its
> place within a project using whatever URL prefix you want.
>
> For instance, a
One thing I really like about the URL mapping/dispatch functionality
of Django is the ability to bring in an existing app and put it in its
place within a project using whatever URL prefix you want.
For instance, a forums app can be included and one project may use:
/forums/topic/2005-05-01/new_
On 10/4/05, Robert Wittams <[EMAIL PROTECTED]> wrote:
>
> This is another ridiculously overcomplicated system that has been
> designed to try to take care of every problem, whilst proliferating
> database entries like there is no tomorrow, and bewildering users and
> administrators beyond belief.
One thing I had complete for a pet framework I was working on (that was
until Django appeared and blew mine away ;) was a "policy" structure
that allowed for ownership and other features that I liked.
I was going to pull it out and re-use it in the project I am working
on, but I figure it is wort
On 9/19/05, Jacob Kaplan-Moss <[EMAIL PROTECTED]> wrote:
>
>
> On Sep 19, 2005, at 11:39 AM, Robert Wittams wrote:
> > Well, I'm not an author of the framework, but the admin code is very
> > hard to understand (imo). I'm sure the authors understand it fine, but
> > for open source to instill co
10 matches
Mail list logo
