Hello all,
I'm fairly new to Django and I noticed a curious behavior of
forms. I noticed that there is no simple way to test a form for a form
not being filled at all. I think it might be a semi-common use case
that you might want to simply not generate a new model instance if a
form has no in
st to someone else.
-AM
On Dec 24, 3:02 pm, Shawn Milochik wrote:
> On Dec 24, 2009, at 2:51 PM, Aristotle Miternan wrote:
>
>
>
>
>
> > Hello all,
>
> > I'm fairly new to Django and I noticed a curious behavior of
> > forms. I noticed that there i
ation I think
my users should be required to remove things they don't want so that
the principle of least surprise is satisfied.
I guess that I don't need it after all. Sorry about that.
-AM
On Dec 24, 3:02 pm, Shawn Milochik wrote:
> On Dec 24, 2009, at 2:51 PM, Aristo
Hello everyone,
The latest update to django 1.2 broke my code and I'm hesitant to
post it as a bug when I'm not sure if there's a core concept that
changed that I don't get.
I noticed that I am no longer able to do this:
class Foo(models.Model):
foo = models.CharField(max_length=30
:
> On Tue, Jan 5, 2010 at 5:52 PM, Aristotle Miternan
> wrote:
> > Hello everyone,
>
> > The latest update to django 1.2 broke my code and I'm hesitant to
> > post it as a bug when I'm not sure if there's a core concept that
> > changed that I don
#x27;, {},
context_instance=RequestContext(request) )
else:
return render_to_reponse( 'sometemplate.html', { 'form' :
myform }, context_instance=RequestContext(request) )
Thanks!
A.M.
On Jan 5, 9:02 pm, Karen Tracey wrote:
> On Tue, Jan 5, 2010 at 8:41 PM,
Thank you very much Russ. I thought I was doing something weird, but I
wasn't sure (I'm very new to Django). I'll give it a shot.
-AM
On Jan 5, 10:38 pm, Russell Keith-Magee
wrote:
> On Wed, Jan 6, 2010 at 11:13 AM, Aristotle Miternan
>
>
>
>
>
> wrote:
>
7 matches
Mail list logo
