Hello All,
It seems I'm facing the same problem or an equivalent problem.
I'll try to use newforms , running python 2.4.3
>>> from django.newforms import *
>>> from listing.models import Industry
>>> w = SelectMultiple()
>>> print w.render('xxx',None,((industrie.id,industrie.fr) for industrie
On Jan 24, 4:47 pm, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote:
> On Jan 24, 1:03 pm, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote:
>
> > On Jan 23, 5:41 pm, "Adrian Holovaty" <[EMAIL PROTECTED]> wrote:
>
> > > Would you be willing to test this out in your local copy of Django,
> > > and
On Jan 24, 1:03 pm, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote:
> On Jan 23, 5:41 pm, "Adrian Holovaty" <[EMAIL PROTECTED]> wrote:
>
> > Would you be willing to test this out in your local copy of Django,
> > and report back?Yes, I will try this and report back. If I create a model
> >
On Jan 23, 5:41 pm, "Adrian Holovaty" <[EMAIL PROTECTED]> wrote:
> Would you be willing to test this out in your local copy of Django,
> and report back?
Yes, I will try this and report back. If I create a model instance from
a form like so: model = Model(**form.clean_data), I also need to
On 1/23/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> I have a form that is incomplete. Error messages are displayed
> correctly. However, if I set LANGUAGE_CODE to 'sv-se' I get the
> following (no other code is altered):
>
> UnicodeEncodeError at /gs/admin/pages/create/
> 'ascii' codec
Ok, I could not reproduce the problem intentionally, but it is back:
I have a form that is incomplete. Error messages are displayed
correctly. However, if I set LANGUAGE_CODE to 'sv-se' I get the
following (no other code is altered):
UnicodeEncodeError at /gs/admin/pages/create/
'ascii' codec
On Dec 30, 8:38 pm, "Adrian Holovaty" <[EMAIL PROTECTED]> wrote:
You shouldn't have to hack around the library like that; it's intended
to handle encoding issues for you. Could you create a ticket (or just
respond here) with the offending data, the offending code and the full
traceback? That
On 12/30/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
I was having problems with newforms as well. I solved it by encoding
all values that might be problematic with .encode('utf-8') and followed
the instructions here:
http://gs.usus.se/2006/12/26/django-i18n-trouble-with-newforms/
Hi
On 12/30/06, Jannis Leidel <[EMAIL PROTECTED]> wrote:
As a matter of fact I did this several times
with a ChoiceField that uses the default select field. But
unfortunately I couldn't get this working with the RadioSelect widget
and got this UnicodeDecodeError:
'ascii' codec can't decode byte
Hi guys,
I recently tried to use the great newforms with a ChoiceField in
combination with a RadioSelect widget. Furthermore I need to compile
the choices on a page view base because I like to manage them from the
admin interface. Additionally the choices can contain special
characters like
On Dec 30, 6:13 pm, Jannis Leidel <[EMAIL PROTECTED]> wrote:
Hi guys,
I recently tried to use the great newforms with a ChoiceField in
combination with a RadioSelect widget. Furthermore I need to compile
the choices on a page view base because I like to manage them from the
admin interface.
Hi guys,
I recently tried to use the great newforms with a ChoiceField in
combination with a RadioSelect widget. Furthermore I need to compile
the choices on a page view base because I like to manage them from the
admin interface. Additionally the choices can contain special
characters like
12 matches
Mail list logo
