On Tuesday 09 May 2017 06:00:31 rmschne wrote:
> > I'm sorry - but this isn't your real error.
> >
> > You will see it in your WSGI daemon logs once you set DEBUG to
> > false.
> >
> >
> >
> > This error is caused by Django trying to print the error using ascii
> > codec for the debug output (I
On May 9, 2017 11:42 AM, Melvyn Sopacua wrote:
> I'm sorry - but this isn't your real error.
Your error is in another castle?
--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, se
Paste the whole stack traceof the error
On 5/9/17, rmschne wrote:
>
>
>> I'm sorry - but this isn't your real error.
>>
>> You will see it in your WSGI daemon logs once you set DEBUG to false.
>>
>>
>>
>> This error is caused by Django trying to print the error using ascii codec
>>
>> for the deb
> I'm sorry - but this isn't your real error.
>
> You will see it in your WSGI daemon logs once you set DEBUG to false.
>
>
>
> This error is caused by Django trying to print the error using ascii codec
> for the debug output (I haven't chased it down any further and I should
> really repor
On Monday 08 May 2017 09:10:15 rmschne wrote:
> I have a Django setup that has worked for a very long time. Yesterday
> I upgraded from Django 1.10 to 1.11.1 and am getting the error:
>
> raise DjangoUnicodeDecodeError(s, *e.args)
> django.utils.encoding.DjangoUnicodeDecodeErrorJón
>
> : 'asc
Yes, it is the first name of a person with a European name, who it's got
that "ó" character. My understanding that it is Unicode. The variable
prints ok in the rest of the code to the screen and in Django templates,
but this __unicode_(self) method fails.
On Monday, 8 May 2017 17:22:42 UTC+1,
What data is "Jón"?
Is it u'J\xf3n' or something else? (print repr(self.fname))
Cheers
Tom
On Mon, May 8, 2017 at 5:10 PM, rmschne wrote:
> I have a Django setup that has worked for a very long time. Yesterday I
> upgraded from Django 1.10 to 1.11.1 and am getting the error:
>
> raise Djan
I have a Django setup that has worked for a very long time. Yesterday I
upgraded from Django 1.10 to 1.11.1 and am getting the error:
raise DjangoUnicodeDecodeError(s, *e.args)
django.utils.encoding.DjangoUnicodeDecodeErrorJón
: 'ascii' codec can't decode byte 0xc3 in position 1: ordinal not
The ordinal error is in GroupRegistration becasue if I rem the group line in
Register the admin works BUT there is no data in GroupRegistration so how can I
have this error?
Caught UnicodeEncodeError while rendering: 'ascii' codec can't encode character
u'\xf6' in position 26: ordinal not in
The unicode error appears to be GroupRegistration but there is *no data* in
that table as yet!
I checked that by rem the inlines in admin.py and separately the grup line in
Register
Caught UnicodeEncodeError while rendering: 'ascii' codec can't encode character
u'
Thanks. It was actually a combination of issues. The database was
UTF8, I should have added to my original post that I could manually
insert and retrieve UTF8 data.
The data we are pulling (migrating one system to a new one, built on
django) is a bit of a nest of encoding issues. So things that ma
Point taken, three times.
On May 24, 9:40 am, Karen Tracey wrote:
> On Mon, May 24, 2010 at 8:27 AM, Scott Gould wrote:
> > > My database and all of its tables are UTF8 encoded with UTF8 collation
> > > (DEFAULT CHARSET=utf8;)
> > > The data I am inputting is unicode
> > > (u'Save up to 25% on y
On Mon, May 24, 2010 at 8:27 AM, Scott Gould wrote:
> > My database and all of its tables are UTF8 encoded with UTF8 collation
> > (DEFAULT CHARSET=utf8;)
> > The data I am inputting is unicode
> > (u'Save up to 25% on your online order of select HP LaserJet\x92s')
> >
> >
> > But when I try to
On Sun, May 23, 2010 at 10:10 PM, vjimw wrote:
> I have been reading up on Unicode with Python and Django and I think I
> have my code set to use UTF8 data when saving or updating an object
> but I get an error on model.save()
>
> My database and all of its tables are UTF8 encoded with UTF8 colla
> My database and all of its tables are UTF8 encoded with UTF8 collation
> (DEFAULT CHARSET=utf8;)
> The data I am inputting is unicode
> (u'Save up to 25% on your online order of select HP LaserJet\x92s')
>
>
> But when I try to save this data I get an error
> Incorrect string value: '\\xC2\\x92s
I have been reading up on Unicode with Python and Django and I think I
have my code set to use UTF8 data when saving or updating an object
but I get an error on model.save()
My database and all of its tables are UTF8 encoded with UTF8 collation
(DEFAULT CHARSET=utf8;)
The data I am inputting is un
Ahh.
There was one foreign key relationship (table not managed under admin)
that i missed. It was indeed returning an int. Fixed it by using
force_unicode and it's now working.
Thanks Karen.
On Jan 6, 7:06 pm, Karen Tracey wrote:
> On Wed, Jan 6, 2010 at 5:20 PM, rc wrote:
> > I get the followi
On Wed, Jan 6, 2010 at 5:20 PM, rc wrote:
> I get the following error when I try and delete a "testcase":
>
> Request Method: GET
> Request URL: http://hades/admin/bisite/testcase/20/delete/
> Django Version: 1.0.2 final
> Python Version: 2.5.2
> Installed Applications:
> [snip]
>
679. ge
I get the following error when I try and delete a "testcase":
Request Method: GET
Request URL: http://hades/admin/bisite/testcase/20/delete/
Django Version: 1.0.2 final
Python Version: 2.5.2
Installed Applications:
['django.contrib.auth',
'django.contrib.contenttypes',
'django.contrib.sessions',
Thanks, Karen. I was using gettext, and replacing it to ugettext
indeed fixed the problem.
On Sep 7, 7:06 pm, Karen Tracey wrote:
> On Mon, Sep 7, 2009 at 12:53 PM, Miklos wrote:
>
> > Hi,
>
> > I have models with verbose names translated into Hungarian. The
> > verbose names contain non-ascii
On Mon, Sep 7, 2009 at 12:53 PM, Miklos wrote:
>
> Hi,
>
> I have models with verbose names translated into Hungarian. The
> verbose names contain non-ascii characters. I have trouble adding,
> editing, or deleting related objects through an admin inline. The
> error I get is below. I can add, ed
n't decode byte 0xc3 in position 1: ordinal not in
range(128)
Unicode error hint
The string that could not be encoded/decoded was: t��mak�
---
The error seems to originate in:
---
django/contrib/admin/options.py in construct_change_message
change_message.append(_(&#x
THANKS
On Mon, Jan 26, 2009 at 10:21 PM, Daniel Roseman <
roseman.dan...@googlemail.com> wrote:
>
> On Jan 26, 8:08 pm, Oleg Oltar wrote:
> > Hi.
> > I want to use django admin, for adding articles into my db. My language
> is
> > Russian.
> >
> > I defined model in the following
On Jan 26, 8:08 pm, Oleg Oltar wrote:
> Hi.
> I want to use django admin, for adding articles into my db. My language is
> Russian.
>
> I defined model in the following way:
>
> from django.db import models
> from tinymce import models as tinymce_models
>
> class Article(models.Model):
> titl
Hi.
I want to use django admin, for adding articles into my db. My language is
Russian.
I defined model in the following way:
from django.db import models
from tinymce import models as tinymce_models
class Article(models.Model):
title = models.CharField(max_length=60)
body = tinymce_mode
Karen,
thank You su much for the help!
after executing "show create table' i realised there was a problem in
my character_set+collation, changed it from latin1_swedish_ci (can't
remember which charset it was)to utf8+utf8_general_ci, and now
everything works like a charm.
Thanks once again!
all
On Sun, Nov 16, 2008 at 10:18 AM, jamesM
<[EMAIL PROTECTED]>wrote:
>
> there is a value 'Qué Onda Guero' in a mysql database. When i SELECT
> this row from mysql, it's displayed correctly. When i connect to mysql
> DB through python 2.6 shell using mySQLObject and assign the value to
> a list, the
there is a value 'Qué Onda Guero' in a mysql database. When i SELECT
this row from mysql, it's displayed correctly. When i connect to mysql
DB through python 2.6 shell using mySQLObject and assign the value to
a list, the >>list_name[0] gives 'Qu\xc3\xa9 Onda Guero', and
>>variable =list_name[0]
Difficult to say there is the error exactly, but I can give few hints
to avoid this error:
1. Define __unicode__() function for all your models, like this:
class BookCategory(models.Model):
shortname = models.CharField(max_length = 765,
verbose_name = _('short
2008/6/24, [EMAIL PROTECTED] <[EMAIL PROTECTED]>:
>
> The unicode stuff continues to give me no end of headaches. This
> morning I keep getting the error below. As near as I can tell, when I
> call AddManipulator it's getting the related fields, and there's a bad
> character somewhere in there.
On Tue, 24 Jun 2008 07:33:14 -0700 (PDT)
"[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote:
>
> The unicode stuff continues to give me no end of headaches. This
> morning I keep getting the error below. As near as I can tell, when I
> call AddManipulator it's getting the related fields, and there's
The unicode stuff continues to give me no end of headaches. This
morning I keep getting the error below. As near as I can tell, when I
call AddManipulator it's getting the related fields, and there's a bad
character somewhere in there. My question is, how can I find it?
"UnicodeEncodeError: 'asci
Kristian,
I had a similar problem when I needed to send some ASCII emails. I
have a snippet at does a translation of unicode characters to close
ASCII approximations if it is helpful:
http://www.djangosnippets.org/snippets/588/
Corey
On Feb 5, 2008, at 3:48 PM, Kristian Øllegaard wrote:
Hi again
Ok - my bad.
Thanks a lot
Regards
Kristian
On Feb 5, 2008 9:29 PM, Jacob Kaplan-Moss <[EMAIL PROTECTED]>
wrote:
>
> On 2/5/08, Kristian Øllegaard <[EMAIL PROTECTED]> wrote:
> > Is there an obvious thing i did wrong? Have you heard about this error
> > before?
>
> This is because of th
On 2/5/08, Kristian Øllegaard <[EMAIL PROTECTED]> wrote:
> Is there an obvious thing i did wrong? Have you heard about this error
> before?
This is because of the changes in Unicode handling after 0.96; read
more here:
http://code.djangoproject.com/wiki/UnicodeBranch#PortingApplicationsTheQuickC
Hi there
I just upgraded from version 0.96, where i without any problems were
running my project. After upgrading, i get an error whenever i
interact with the database (tried to read, add or edit).
'ascii' codec can't encode character u'\xd8' in position 0: ordinal
not in range(128)
Is there a
with the Traceback. If a
Unicode
error appears, the values in the traceback seems to be unicode. But this is not
true. The data from the database are byte strings.
I have made a Patch for the file ./django/db/backends/mysql_old/base.py to fix
the unicode problem. You can find the Patch in the
Changed mysql db Collation to utf8_unicode_ci and the error was gone
! thanks
yours,
Sandro
Thomas Guettler wrote:
> Am Mittwoch, 22. August 2007 19:25 schrieb Sandro Fernandes:
>
>> Hi all ,
>>
>> I runing Django from the trunk and getting the error bellow , this
>> happens when a da
Am Mittwoch, 22. August 2007 19:25 schrieb Sandro Fernandes:
> Hi all ,
>
> I runing Django from the trunk and getting the error bellow , this
> happens when a data has accents like á é or ã
>
>
> UnicodeDecodeError at /admin/frete/frete/
>
If you use the current SVN version with includes this
39 matches
Mail list logo
