Hi,
I'm sorry for asking this here, but the question was raised several
time on the -users mailing list and I don't think we users have a
solution for it.
Basically, the problem is that if I call a templatetag into a block
and it fills me a variiable with the usual context[varname]=something,
then
Hi,
I've also asked on the users ml but got no anwser. Maybe you can
undestand the question better?
Hi,
I have a couple of models like:
class Album(models.Model):
title = models.CharField(max_length=255)
class Image(models.Model):
image = models.ImageField(upload_to='images/')
albums =
On Tue, Dec 16, 2008 at 11:55 PM, Alex Rades wrote:
> On Tue, Dec 16, 2008 at 5:49 PM, James Bennett wrote:
>>
>> On Tue, Dec 16, 2008 at 10:21 AM, Alberto Donato
>> wrote:
>>> I don't see any downside in this proposal.
>>
>> His proposal
On Tue, Dec 16, 2008 at 5:49 PM, James Bennett wrote:
>
> On Tue, Dec 16, 2008 at 10:21 AM, Alberto Donato
> wrote:
>> I don't see any downside in this proposal.
>
> His proposal seems to center around forcibly making "objects" *always*
> be a manager returning an unfiltered QuerySet, so I'm not
On Mon, Dec 15, 2008 at 3:12 PM, Karen Tracey wrote:
> On Mon, Dec 15, 2008 at 5:51 AM, Alex Rades wrote:
>>
>> Hi,
>> my understanding about custom managers is that if you want to define a
>> custom manager, you also HAVE to remember to define the "objects&q
Hi,
my understanding about custom managers is that if you want to define a
custom manager, you also HAVE to remember to define the "objects"
manager first, otherwise some parts of django (eg. admin) will not
work.
I find this suboptimal.
I think that "objects" should always be the default manage
On Tue, Sep 2, 2008 at 5:15 PM, Jacob Kaplan-Moss
<[EMAIL PROTECTED]> wrote:
>
> Hi folks --
>
> We're about to push out 1.0rc1. Check the blog for the announcement.
> Things to know
>
> #8669 is the only known code bug. Malcolm or I will fix it tonight or
> tomorrow morning.
Hi,
http://code.djan
Hi,
validator_list in model fields (and maybe in form fields too) isn't
working at the moment.
Could we remove it from the docs?
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to
On Fri, Aug 22, 2008 at 9:42 PM, Don Spaulding <[EMAIL PROTECTED]> wrote:
>
>
> On Fri, Aug 22, 2008 at 12:12 PM, Alex Rades <[EMAIL PROTECTED]> wrote:
>>
>> Hi,
>> Is there a reason for checkboxes (BooleanField) in admin having the
>> label on t
<[EMAIL PROTECTED]> wrote:
>
> On Fri, Aug 22, 2008 at 1:12 PM, Alex Rades <[EMAIL PROTECTED]> wrote:
>>
>> Hi,
>> Is there a reason for checkboxes (BooleanField) in admin having the
>> label on the right side instead of left?
>
> Isn't that ho
Hi,
Is there a reason for checkboxes (BooleanField) in admin having the
label on the right side instead of left?
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send
Hi,
is there a non-obvious reason for signals like post_save being
triggered twice for each save?
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django
Oops I've sent accidentally a draft of this mail 2 minutes ago, while i was
still writing it. Please read this one.
In nfa, IPAddressField with psycopg2 is not working (neither is XMLField, as
already reported, but lets focus on the IPAddressField).
There is a ticket with a patch at:
http://code.
Hi,
in nfa, IPAddressField with psycopg2 is not working (neither is XMLField, as
already reported, but lets focus on the IPAddressField).
There is a ticket with a patch at:
http://code.djangoproject.com/ticket/5622
The situation is that in some db, IPAddressField is treated as
I've tried the pat
, 2008 at 10:19 PM, TiNo <[EMAIL PROTECTED]> wrote:
> How about creating a widget that just displays the data? Then override the
> form and use this widget instead of the default widget.
>
>
> On Fri, Jul 4, 2008 at 6:14 PM, Alex Rades <[EMAIL PROTECTED]> wrote:
>
>&g
Hi,
I'm writing an application which makes a pretty heavy use of the
newforms-admin administrative site.
One recurring need is displaying of informative fields (fields which should
not be editable from the admin site, but only viewed).
For example, imagine to have a DateField field into a Story cl
Shouldn't this be marked as somewhat blocking for 1.0-alpha? Is there any
good reason why the code you wrote has not been accepted?
On Tue, Jul 1, 2008 at 6:46 PM, David Danier <[EMAIL PROTECTED]>
wrote:
>
> > I'm trying to understand what's wrong with the XMLField in nfa.
> > The validation in v
Hi,
I'm trying to understand what's wrong with the XMLField in nfa.
The validation in validators.py/RelaxNGCompact is never called, It looks
like unused dead code. This means the validation on XMLFields is currently
not working at all.
Is there anyone with a better understanding of the situation?
18 matches
Mail list logo
