On Fri, 2006-08-11 at 08:24 -0500, Jeremy Dunck wrote:
> On 8/11/06, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote:
> > On Fri, 2006-08-11 at 11:52 +, Michele Cella wrote:
> > > Adrian Holovaty wrote:
> > > I'm not actually using django (yet) but I always wondered why you
> > > weren't using ca
On 8/11/06, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote:
> On Fri, 2006-08-11 at 11:52 +, Michele Cella wrote:
> > Adrian Holovaty wrote:
> > I'm not actually using django (yet) but I always wondered why you
> > weren't using callables directly, it's really more intuitive and
> > pythonic, wh
On Fri, 2006-08-11 at 11:52 +, Michele Cella wrote:
> Adrian Holovaty wrote:
> >
> > I must say, I'm really excited about this change. I've been converting
> > my own stuff to it, and it feels more natural.
> >
>
> I'm not actually using django (yet) but I always wondered why you
> weren't us
Adrian Holovaty wrote:
>
> I must say, I'm really excited about this change. I've been converting
> my own stuff to it, and it feels more natural.
>
I'm not actually using django (yet) but I always wondered why you
weren't using callables directly, it's really more intuitive and
pythonic, what ab
On 6/26/06, Simon Willison <[EMAIL PROTECTED]> wrote:
> I've been playing around with making the URL resolver accept a
> callable in addition to accepting 'module.blah' strings, and I think
> it's a big improvement.
OK, we've gained this functionality as of
http://code.djangoproject.com/changeset
On 26 Jun 2006, at 11:51, Daniel Poelzleithner wrote:
> What i still missing is a possibility to use other values to find the
> right view (most likely the http host header).
> I suggested http://code.djangoproject.com/ticket/1192 but Adrian
> doesn't
> like it for some reason I can't understa
Simon Willison wrote:
> Allowing callables in urlconfs opens up a whole bunch of other
> opportunities as well. Setting up generic views could be made much
> less fiddly:
What i still missing is a possibility to use other values to find the
right view (most likely the http host header).
I su
+1 for the patch. If you don't want to put logics in urls.py put it
into url_logics.py and import from urls ;)
The patch really makes things look better
--
Sincerely,
Vladimir "Farcaller" Pouzanov
http://www.hackndev.com
--~--~-~--~~~---~--~~
You received this m
Malcolm Tredinnick wrote:
> Another thing we need to document better here, because this claim is not
> quite correct (didn't you help write this?). The patterns() function
> returns a normal Python list. So you can just append successive calls to
> patterns() to each other:
>
> urlpattern
On 26 Jun 2006, at 11:04, Malcolm Tredinnick wrote:
> Another thing we need to document better here, because this claim
> is not
> quite correct (didn't you help write this?).
D'oh. No, the pattern prefixing stuff was nothing to do with me. Not
sure how I missed that trick!
Cheers,
Simon
On Mon, 2006-06-26 at 10:30 +0100, Simon Willison wrote:
> I've been playing around with making the URL resolver accept a
> callable in addition to accepting 'module.blah' strings, and I think
> it's a big improvement.
>
> The change itself is very simple - when a URL is resolved, callable
>
I've been playing around with making the URL resolver accept a
callable in addition to accepting 'module.blah' strings, and I think
it's a big improvement.
The change itself is very simple - when a URL is resolved, callable
(callback) is used to decide if the callback is already a callable
12 matches
Mail list logo
