On Apr 14, 3:51 pm, Jannis Leidel wrote:
> Yeah, please open a ticket, this is defintiely something we need to document
> since the behaviour changed in 1.3.
I opened #15830 (http://code.djangoproject.com/ticket/15830).
Thanks Jannis.
--
You received this message because you are subscribed to
On Apr 14, 1:52 pm, Ramiro Morales wrote:
> On Thu, Apr 14, 2011 at 7:51 AM, Fidel Ramos wrote:
> > I included some fields from localflavor.es.forms in a project, and
> > expected the error messages to appear translated, as localflavor
> > already has a catalog. Howe
I included some fields from localflavor.es.forms in a project, and
expected the error messages to appear translated, as localflavor
already has a catalog. However the messages only appeared in English.
Turns out the localflavor catalog is not automatically loaded, it must
be included manually in t
On Apr 21, 12:04 am, Marc Garcia wrote:
> just to warm up for my Google Summer of Code on i18n, I want to start
> a discussion on to simple things...
I'm glad to see something is going to finally get done in i18n and
l10n, which mostly sucks right now.
> First thing is where to place l10n setti
On 28 mar, 20:58, Justin Bronn wrote:
> I see what you're talking about now, and I agree it's a bug. Please
> open up a ticket and we'll consider the design decisions there.
> Thanks for the clarification.
I did just that, it's ticket #10660: http://code.djangoproject.com/ticket/10660
I don't
On 27 mar, 19:49, Justin Bronn wrote:
> Isn't the checking of `self.null` that you've identified as the
> problem already in the `GeometryField.clean` method? Are you
> proposing a recursive call?
>
> I agree that GeometryField is ripe to be improved -- but I'm unclear
> on exactly what is the p
django.contrib.gis.forms.fields.GeometryField completely ignores the
required attribute in its clean() method. Instead it checks if the
model field is nullable, which needlessly ties forms and model code. I
realized this because I have a model with a non-nullable GeometryField
but need a non-requi
date_hierarchy is broken for me when filtering models with a nullable
date field and at least one instance is None. It raises an
AttributeError " 'NoneType' object has no attribute 'year' ". It seems
the error could be in line 265 of admin's admin_list.py.
Could someone confirm to open a ticket i
