On Sep 12, 3:42 pm, Malcolm Tredinnick <[EMAIL PROTECTED]>
wrote:
> So whilst adding it is consistent, it's not really a common way to use
> translation and shouldn't be necessary for that patch.
True, I was getting confused about __all__
Anyway, the ticket now contains full tests and docs. Feel
On Wed, 2007-09-12 at 03:34 +, SmileyChris wrote:
[...]
> PS: I'm no internationalization expert, but ugettext_lazy wasn't in
> __all__ of django.utils.translation.__init__ so I had to add it in to
> use it. I'm not overlooking something, am I?
Well, you are and you aren't. You don't need to
I've added a functional patch to the ticket
http://code.djangoproject.com/ticket/3457
if some people want to try it out.
Feel free to write some documentation or tests. ;)
PS: I'm no internationalization expert, but ugettext_lazy wasn't in
__all__ of django.utils.translation.__init__ so I had t
On 4/8/07, Ceph <[EMAIL PROTECTED]> wrote:
>
> There's an open ticket currently regarding custom error messages in
> newforms: http://code.djangoproject.com/ticket/3457
>
> I currently have an ugly hack in place that gives me an error_message=
> parameter for the field types I use, but, it's ugly,
There's an open ticket currently regarding custom error messages in
newforms: http://code.djangoproject.com/ticket/3457
I currently have an ugly hack in place that gives me an error_message=
parameter for the field types I use, but, it's ugly, and doesn't work
entirely. I'm working on getting a r
