On Tuesday 07 February 2006 00:32, I wrote:
> I did have a patch at one point that made RelatedManager a subclass
> of firstly QuerySet, secondly Manager (which was the right way around
> for the __init__ etc to work). However I had problems with it - I
> think mainly to do with .add() (and now
On Monday 06 February 2006 23:13, Luke Plant wrote:
> - thrashing out some issues:
Here is another thing. I don't like that you currently have to do this
in templates:
{% for foo in bar.foo_set.all %}
...
{% endfor %}
instead of
{% for foo in bar.foo_set %}
...
{% endfor %}
I did have a p
On Monday 06 February 2006 23:13, Luke Plant wrote:
> Some things that are still to be done in the current batch of
> changes:
I forgot to mention the generic views - I converted the 'list_detail'
ones but none of the others.
Luke
--
I teleported home one night
With Ron and Sid and Meg,
Ron
Some things that are still to be done in the current batch of changes:
- add tests and implementation for o2m .clear() and .remove() methods
- work out what these methods (clear and remove) should return, if
anything e.g. True if something was changed. This is especially
relevant for the mani
Here are my two cents,
Clearly some work will need to be done to the current authentication
system to make it more modular for those that have LDAP, OpenID, etc,
as "requirements" for there projects. Having an easy to define
authentication mechanism as Brian proposed is also very attractive. M
> > Thanks. I'll try now.
> >
>
> But the problem is still existed.
>
> It is:
>
> Exception Type: AttributeError
> Exception Value: 'Post' object has no attribute 'set_tags'
This is a different error - the manipulators need to be updated using
.add() and .clear(), which don't exist ye
Luke Plant wrote:
> Jason Davies wrote:
>
> > 1. Get rid of the 'Package' model - is there any use for it now that
> > the magic has gone?
> > 2. Replace ContentType's 'package' and 'python_module_name' fields with
> > a 'model' field.
>
> +1 - the 'Package' table now seems to contain two columns
Jason Davies wrote:
> 1. Get rid of the 'Package' model - is there any use for it now that
> the magic has gone?
> 2. Replace ContentType's 'package' and 'python_module_name' fields with
> a 'model' field.
+1 - the 'Package' table now seems to contain two columns with
identical content. Just t
2006/2/6, limodou <[EMAIL PROTECTED]>:
> 2006/2/6, Luke Plant <[EMAIL PROTECTED]>:
> >
> > Fixed now.
> > http://code.djangoproject.com/ticket/1331
> >
>
> Thanks. I'll try now.
>
But the problem is still existed.
It is:
Exception Type: AttributeError
Exception Value:'Post' obje
2006/2/6, Luke Plant <[EMAIL PROTECTED]>:
>
> Fixed now.
> http://code.djangoproject.com/ticket/1331
>
Thanks. I'll try now.
--
I like python!
My Blog: http://www.donews.net/limodou
NewEdit Maillist: http://groups.google.com/group/NewEdit
Fixed now.
http://code.djangoproject.com/ticket/1331
Luke
limodou wrote:
> I knew that I can use Descriptor fields to manipulate the tablewide
> query, but it seems that many codes also using old-style query, just
> like get_tag_list, but not the new-style tags.add(), etc.
Yep, this bit hasn't been converted yet (there are still a number of
places tha
12 matches
Mail list logo