I've submitted #10697 with the following problem statement. Please
comment.
---
Suppose I have a complex admin page that, given the following models:
class A(models.Model):
name = models.CharField(...)
# 10 more fields, some of them e.g. TextFields()
def __unicode__(self):
I noticed an important change in behaviour between Django 1.0.2 and
Django 1.1+ (svn and beta versions).
If I set a signal that intercepts as pre_save and try to access a
FileField/ImageField's path, I don't get the same result. It seems the
'upload_to' attribute is not taken into account!
It see
On Thu, Apr 2, 2009 at 8:59 AM, Lior Gradstein wrote:
>
> I noticed an important change in behaviour between Django 1.0.2 and
> Django 1.1+ (svn and beta versions).
>
> If I set a signal that intercepts as pre_save and try to access a
> FileField/ImageField's path, I don't get the same result. It
Malcolm,
I'm just following up on my last post. I have gone over the django-
restapi library and would appreciate more guidance on the intended
direction of the project. As you suggested, following up on the
existing work there is a great way to get this feature to the public
this summer.
Than
On Thu, Apr 2, 2009 at 11:45 AM, Karen Tracey wrote:
> I think it's a bug, and I'm pretty sure it was introduced by r9766. The
> setting of the actual file name that will be used (which pulls in the
> upload_to path and possibly tacks on some underscores if the uploaded name
> conflicts with al
I'm short on time right now so I just want to respond to one part of this
that I just noticed and I'll come back later to digest the rest. Thanks for
the background on the why to r9766. I knew it was model-validation related
but didn't know what the specific issue was. It helps to have a clearer id
Hey all, I was considering putting on a Dallas sprint for 1.1. I'm
not sure exactly when 1.1 will ship, but soon-ish, so I was thinking
about trying to make the sprint the weekend of 4/10 (Easter weeked) or
4/17.
Any preference? Who can make it or will consider making it?
--~--~-~--~--
I think that the attached patch corrects the problem.
Is there still something missing in order to get it into trunk?
Thanks!
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to
On Thu, Apr 2, 2009 at 1:55 PM, Matias Surdi wrote:
>
> I think that the attached patch corrects the problem.
>
> Is there still something missing in order to get it into trunk?
>
>
> Thanks!
>
>
> >
>
It is, at a minimum missing tests.
Alex
--
"I disapprove of what you say, but I will defend
On Thu, 2009-04-02 at 09:15 -0700, Bill Konrad wrote:
> Malcolm,
>
> I'm just following up on my last post.
A whole 12 hours after the previous one. I had a day away from mail.
That happens sometimes.
> I have gone over the django-
> restapi library and would appreciate more guidance on the i
On Thu, Apr 2, 2009 at 2:24 PM, Russ wrote:
>
> Thanks for the many, many pointers, Russ. Better ways of thinking
> about the problem have finally caught up to me. To illustrate my
> latest thoughts,
>
> class DefaultStructure(serializers.Structure):
> root_list = ("django-objects", {"versio
11 matches
Mail list logo
