also sprach James Bennett [2009.05.25.2047 +0200]:
> And, really, this is the sort of thing that leads me to say it
> shouldn't be in contrib right now. We do need to have some sort of
> document outlining criteria, but I'd like to think that commitment to
> a stable API
On Mon, May 25, 2009 at 12:43 PM, martin f krafft wrote:
> Look what I found! Check out the fifth point, labeled #1, top-most
> annoyance with Python, in
And?
While I like it as much as the next guy, django-tagging, to take your
example, is currently sitting at version
also sprach Dougal Matthews [2009.05.23.1823 +0200]:
> Fair enough. I don't really have an issue with the idea, could be
> quite handy.
>
> I can just imagine them saying no :) so thought I would question
> it as a move/idea.
Look what I found! Check out the fifth point,
Fair enough. I don't really have an issue with the idea, could be quite handy.
I can just imagine them saying no :) so thought I would question it as
a move/idea.
Also, might be a good idea to wait until 1.1 is out the door so they
have time to consider it properly...
Dougal
On 23/05/2009,
also sprach Dougal Matthews [2009.05.23.1103 +0200]:
> I don't think tagging is a particularly hard or non-trivial.
No. All the more reason to push for a standard and prevent dozens
of different implementations, no?
> Anyway, this conversation is a bit irrelevant because;
I've never actually used it in any work related projects. I've only used it
in personal messing around type projects...
> Good contrib packages tackle issues that that are not trivial, are bikeshed
> prone, and are difficult to get right for the common case.
I don't think tagging is a
also sprach Kai Kuehne [2009.05.23.1048 +0200]:
> > Pretty must everybody does seem to use django-tagging unless
> > they have some special weird use-case.
>
> Huh? Can you remove that "everybody", please? I've never used
> tagging and I'm confident - many others too.
I
Hi,
On Fri, May 22, 2009 at 11:52 PM, Dougal Matthews wrote:
> Pretty must everybody does seem to use django-tagging unless they have some
> special weird use-case.
Huh? Can you remove that "everybody", please? I've never used tagging
and I'm confident - many others too.
also sprach Dougal Matthews [2009.05.23.0232 +0200]:
> It doesn't. Why should it?
Well, because django-tagging is, quote Jacob:
- optional
- de-facto standard
- the implementation of a common pattern
Tagging is a very common feature nowadays, isn't it? Having tag
On 23 May 2009, at 02:32 , Dougal Matthews wrote:
> It doesn't. Why should it?
>
To be blessed at the "true standard" for tagging, the way third-party
python modules are pulled into the stdlib?
--~--~-~--~~~---~--~~
You received this message because you are
It doesn't. Why should it?
---
Dougal Matthews - @d0ugal
http://www.dougalmatthews.com/
2009/5/22 martin f krafft
> also sprach Dougal Matthews [2009.05.22.2352 +0200]:
> > Pretty must everybody does seem to use django-tagging unless they have
> some
also sprach Dougal Matthews [2009.05.22.2352 +0200]:
> Pretty must everybody does seem to use django-tagging unless they have some
> special weird use-case.
>
> I've used it every time I've needed tagging and don't have a gripe with it
> yet.
So how would it find its way
Pretty must everybody does seem to use django-tagging unless they have some
special weird use-case.
I've used it every time I've needed tagging and don't have a gripe with it
yet.
Cheers,
Dougal
---
Dougal Matthews - @d0ugal
http://www.dougalmatthews.com/
2009/5/22 martin f krafft
also sprach Alex Gaynor [2009.05.22.1545 +0200]:
> http://jacobian.org/writing/what-is-django-contrib/ here is
> a description of what one of the core developers see as the role
> of django contrib. It should be noted that 2 of the core devs
> said at euro django con that
14 matches
Mail list logo