It looks like you have named one of your model classes with a name
that contains a non-ASCII character. Stick with class names with only
a-z, A-Z, 0-9 characters and see if that helps.
On 21 January 2014 10:29, Edgar Reyes wrote:
> Hi, I'm looking in google search about this error but I didn't fi
Just in case someone else run in the same problem, I have found a solution.
It is explained here: https://code.djangoproject.com/ticket/17566
HTH Vitalije
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To view this discussion on the web visi
I have found ticket that was closed because more information was needed but
not provided. It seems that it is related to my question. So I reopened
ticket and pasted log information from the above message. If anyone would
like to see it, here is the link:
https://code.djangoproject.com/ticket/1
On Friday, August 10, 2012 4:30:19 PM UTC+2, Mengu wrote:
>
> do you have "# -*- coding: utf-8 -*-" at the top of your file?
>
>
Yes I have. If I had not that line, python2.7 would not accept file with
non ascii characters in it. It appears that everything is working fine
except when django tri
do you have "# -*- coding: utf-8 -*-" at the top of your file?
On Friday, August 10, 2012 4:29:01 PM UTC+3, vitalije wrote:
>
> Hello,
> I have recently updated my django installation to version 1.4.
> When I try to get an url that doesn't have a match in urlpatterns,
> django-server replies wi
FYI I get the same problem on Ubuntu 10.04 LTS:
Traceback (most recent call last):
File "server/manage.py", line 11, in
execute_manager(settings)
File
"/home/user/.ve_config/myproject/lib/python2.7/site-packages/django/core/management/__init__.py",
line 438, in execute_manager
util
thnx mate its working now ;)
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-users@googlegroups.com.
To unsubscribe from this group, send email to
django-users+unsubscr...@googlegroups.com.
For more o
Your problem is the curly quotes around “Times New Roman”. First, they
will prevent CSS from seeing the font as Times New Roman, and second,
they are encoded with the byte 0x93, which is how they show up in the
various Windows code pages (cp1252, for instance). Convert your file to
UTF-8, if you
I would hazard a guess that your index.html file is actually not ascii
or utf-8 but some other encoding - probably cp1252
0x93 in cp1252 is a "smart quote" ( see
http://en.wikipedia.org/wiki/Windows-1252 ) so that would look like it
fits with the line quoted below.
Open it in an editor that knows
http://www.adobe.com/go/getflash";>
http://www.adobe.com/images/shared/
download_buttons/get_flash_player.gif" alt="Get Adobe Flash player"/>
About Us
Lorem ipsum dolor sit amet, consectet
i will post my index page now
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-users@googlegroups.com.
To unsubscribe from this group, send email to
django-users+unsubscr...@googlegroups.com.
For more
Also, don't forget about the magic functions provided by django:
smart_unicode and smart_str
On Jan 5, 2:27 pm, Karen Tracey wrote:
> On Thu, Jan 5, 2012 at 8:16 AM, César Frias wrote:
> > I guess you have some files without the # -*- coding: utf-8 -*- on the top
> > of the file
>
> > You will n
On Thu, Jan 5, 2012 at 8:16 AM, César Frias wrote:
> I guess you have some files without the # -*- coding: utf-8 -*- on the top
> of the file
>
> You will need this if you want to use some letters like é or ç...
>
>
No, you get a different exception if you are missing the encoding
declaration in
I guess you have some files without the # -*- coding: utf-8 -*- on the top
of the file
You will need this if you want to use some letters like é or ç...
Att,
César Frias
Linux user: #506849
Twitter: twitter.com/cesarFrias
2012/1/5 Piotr Zalewa
> Please attach the index.html - there might b
On Thursday, 5 January 2012 11:18:52 UTC, Hassan wrote:
>
> Dear ALL,
>
> i am trying to do render_to_response('index.html') , and i keep geting
> this dont know why ? its a normal html page ??!! what to do ?
>
You need to post some code.
However 99 times out of 100, when you see this error
Please attach the index.html - there might be an unknown unicode character
zalun
On 01/05/12 12:18, Hassan wrote:
Dear ALL,
i am trying to do render_to_response('index.html') , and i keep geting
this dont know why ? its a normal html page ??!! what to do ?
UnicodeDecodeError at /
'utf8' code
On Thu, Mar 3, 2011 at 8:24 AM, Karen Tracey wrote:
> A real fix I believe would need to be made to the Python library code to
> ensure that it doesn't die if the windows registry contains non-ASCII data.
>
In fact there is a bug open in the Python bug tracker for this:
http://bugs.python.org/i
Dear friends!
Karen Tracey gave me great reference:
http://www.google.com/url?sa=D&q=http://groups.google.com/group/django-users/msg/7fe07998db471693
There is reference to original work:
http://victor-k-development.blogspot.com/2010/07/unicodedecodeerror-django.html
Victor discovered a cause of thi
On Thu, Mar 3, 2011 at 8:57 AM, Perses Titan wrote:
> In your case, most probably django crashs when it reads nonASCII
> characters from DB.
>
>
No. The posted traceback clearly shows where the error is occurring and it
is nowhere in Django. As I posted earlier it looks like a bug in the Python
l
Hello!
I got the same error when i tried to work with Cyrillic charset in
Python.
In my case it was pure Python problem.
Here is good explanation why it happened:
http://docs.python.org/howto/unicode.html
and http://python.su/forum/viewtopic.php?pid=6476 (rus)
In your case, most probably django
On Thu, Mar 3, 2011 at 4:01 AM, Vladimir wrote:
> 1. web browser does not give messages, in command line I see:
> Traceback (most recent call last):
> File "C:\Python27\lib\site-packages\django\core\servers\basehttp.py",
> line 280, in run
>self.result=application(self.environ, self.start_res
Thank You very much!
It is set by default but there is no error message. Some days ago,
when I had another problem, web browser showed messages.
On 3 мар, 12:10, "Szabo, Patrick \(LNG-VIE\)"
wrote:
> If you want to see errors in the browser you might want to set "DEBUG = True"
> in your setting
m
> Auftrag von Vladimir
> Gesendet: Donnerstag, 03. März 2011 10:01
> An: Django users
> Betreff: Re: UnicodeDecodeError: 'ascii' codec can't decode byte 0xe0 in
> position 0: ordinal not in range(128)
>
> 1. web browser does not give messages, in command line I s
1. web browser does not give messages, in command line I see:
Traceback (most recent call last):
File "C:\Python27\lib\site-packages\django\core\servers\basehttp.py",
line 280, in run
self.result=application(self.environ, self.start_response)
File "C:\Python27\lib\site-packages\django\core\serv
On Thursday, March 3, 2011 6:48:21 AM UTC, Vladimir wrote:
>
> Good morning!
> In me first exercise project with Django I met an error message:
> UnicodeDecodeError: 'ascii' codec can't decode byte 0xe0 in position
> 0: ordinal not in range(128). Admin pages are built without css.
> Then I chan
There is a ticket with patch for this problem here:
http://code.djangoproject.com/ticket/14235
Karen
--
http://tracey.org/kmt/
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-us...@googlegroups.com.
Hi Bill, thanks for the valuable inputs. I could hit a better solution
and I believe that is simplest one. Better, the solution is on the
application side and not on the DJango side.
What I did was this -
When my parser starts reading data from files (for which I don't know
the encoding), it first
I don't really have enough context (or, at the moment, time) to do a
serious review. It may well be that you are safe. iri_to_uri () looks
like the key, since you almost certainly will trip over a value that isn't
eligible as a url (clients cut and paste from MS Word and equivalent
all the time).
Ok, I did some changes and things look to be working.
My intention was to receive URLs, parse them to get the base URL, put
them in database (Postgres), and then through a http query, through
Django interface through psycopg2, retrieve these URLs and display
those to the user on the browser in a t
Hi Bill,
Thanks.
You were right. The Postgres encoding and Django encoding are
different.
The parser is Python. Postgres encoding was SQL_ASCII. I changed it to
UTF8, and the parser failed to insert in DB!! I believe I need to fix
it first.
--
You received this message because you are subscribe
I doubt that you can fault Postgres. It doesn't need to care about
the encoding of contents, other than it must find the end of the string
(and the conventions used may depend on the interface and
connection settings).
When you say contents of a url, do you mean the url itself, or the
page referr
Awesome, I had exactly the same problem and by chance we're on
Rackspace too.
I added the two lines to that file exactly as shown in the Django
docs, restarted httpd, and now Sorl can handle thumbnails with unicode
chars in them.
cheers
On Jun 27, 4:44 pm, Federico Capoano wrote:
> Thanks for y
Thanks Bill.
Do you mean even Postgres also should have thrown errors?
My worry is different here. The characters that I am getting are valid
contents of a HTTP URL, and my parser is able to parse them and put in
database. However, the Django interface is not able to read it. If I
am required to a
What's in the database probably isn't legal UTF-8. It is easily possible
to have a sequence of characters in some other encoding which only
results in the wrong characters if treated as UTF-8, but it is also possible
to violate the UTF-8 structure with such a sequence. PostgreSQL, if
set for UTF-
Thanks for your help. I've been able to fix the problem thanks also to
the Rackspace technical support.
This is the answer, i post it cos it might be useful to someone else:
"Greetings,
I've added the two lines you provided to /etc/sysconfig/httpd - a file
which is 'sourced' by the apache startu
Federico,
When trying out what Karen suggests then in the unlikely event that
Red Hat doesn't load the environment variables from /etc/apache2/
envvars, one way to find it without consulting documents is to look at
the apache start-up script (e.g. /usr/sbin/apache2ctl) so find that on
your server
On Sun, Jun 20, 2010 at 5:15 AM, Federico Capoano
wrote:
> I logged onto the server via SSH and tried the command "locale", the
> following is what I get:
>
> LANG=en_US.UTF-8
>
[snipped remainder]
That looks fine, but the locale when you ssh into the server is not
necessarily the same as the loc
I logged onto the server via SSH and tried the command "locale", the
following is what I get:
LANG=en_US.UTF-8
LC_CTYPE="en_US.UTF-8"
LC_NUMERIC="en_US.UTF-8"
LC_TIME="en_US.UTF-8"
LC_COLLATE="en_US.UTF-8"
LC_MONETARY="en_US.UTF-8"
LC_MESSAGES="en_US.UTF-8"
LC_PAPER="en_US.UTF-8"
LC_NAME="en_US.UT
The same code on my computer offline works without problems, so I
guess It's a server configuration problem, what do you think?
I read the this bit here:
http://docs.djangoproject.com/en/dev/howto/deployment/modpython/#if-you-get-a-unicodeencodeerror
And it says to write something similar to:
ex
> File "/usr/lib/python2.3/site-packages/sorl/thumbnail/utils.py",
> line 36, in all_thumbnails
> if os.path.isfile(os.path.join(path, file)):
>
> File "/usr/local/lib/python2.6/posixpath.py", line 68, in join
> path += b
>
> UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in
On Mon, Jun 14, 2010 at 10:12 AM, Federico Capoano wrote:
> Hello to all.
>
> Version 1.2.1:
>
> In the admin, just noticed that when I delete any of the dynamic
> inlines (an image basically) of a form and then I hit the SAVE button
> the image is deleted successfully but I get this error:
>
> U
Maybe feed your templates through a call to unicode.decode, with the
errors arg set to 'replace'? This will replace all sequences that
can't be decoded with a '?'. At least that lets you render the
template. Depending on how far you want to go, you could also write
your own error handler and replac
I had a similar problem and I used two approaches. First I used Django's
smart_str:
from django.utils.encoding import smart_str
text = smart_str(text)
Then I had the same problem with fields using the csv module and I used
these functions that I found on the web:
def unicode_csv_reader(unicode_c
I offer my condolences.
Technical solutions to political problems are seldom completely satisfactory.
One possibility is that he doesn't actually get access to the
templates directory,
but gets read access to that directory, and write access to another directory,
from which a script that he can i
On Sun, May 31, 2009 at 6:24 AM, Vlad(L) wrote:
>
> The second day I fight, I can not troubleshoot. I wish to output in
> django blog page, and to me produces UnicodeDecodeError.
> I have filled a blog with the Russian text, and was English probably
> error would not be. Here an error code:
>
>
>
Thanks for the quick reply.
I almost gave up, but I just found something that seems to work for
me.
So I've tried:
---
filename = codecs.BOM_UTF8.decode(postfile['filename'])
---
...which gave a LookupError.
Then I tried casting to Unicode:
---
filename = unicode(postfile['filename'])
---
...whi
On Wed, 2008-11-26 at 06:20 -0800, gnijholt wrote:
> Hello,
>
> I'm running Django r7548 using PostgreSQL 8.3 on Leopard.
> The problem: When I upload a file with a filename like '.jpg', I
> get the following error:
> ---
> UnicodeDecodeError at /library/documents/12114/addFile/
> 'ascii' c
On Thu, 2008-10-23 at 23:14 -0400, Chuck Bai2 wrote:
> I have a contact form which send email. It is working fine. But when I try to
> add two Unicode to subject line:
>
> subject = "DOMAIN.COM 留言 - %s (%s)" % (full_name,location)
The string portion of this (the "DOMAIN.COM ..." bit) is not a
On Sep 4, 4:00 pm, "Karen Tracey" <[EMAIL PROTECTED]> wrote:
> In the working case your initial string is a bytestring, in the non-working
> case the initial string is unicode. The error comes from trying to replace
> into a unicode string a bytestring containing non-ascii chars:
>
> >>> s = u'as
2008/9/4 Aljosa Mohorovic <[EMAIL PROTECTED]>
>
> i can't figure out what's the problem (i also used re with same
> results). how should i replace a pattern with non-ascii char?
>
> working as expected:
> In [27]: s
> Out[27]: 'asd'
> In [28]: s = s.replace("s", "š")
> In [29]: s
> Out[29]: 'a\xc5
On Aug 20, 4:05 pm, "Karen Tracey" <[EMAIL PROTECTED]> wrote:
> Also most of these settings in DATABASE_OPTIONS are unnecessary. The only
> one that you really need if it is not your database default storage engine
> is "SET storage_engine=InnoDB".
I've eliminate DATABASE_OPTIONS and this solve
I've tested the application with sqlite instead of mysql and I've no
problems.
The mysql table that syncdb generate is (the mysql dump):
DROP TABLE IF EXISTS `demo_mymodel`;
SET @saved_cs_client = @@character_set_client;
SET character_set_client = utf8;
CREATE TABLE `demo_mymodel` (
`id` i
On Aug 20, 4:05 pm, "Karen Tracey" <[EMAIL PROTECTED]> wrote:
>
> Have you defined a __unicode__ method for your model? If yes, what does it
> look like? Also are you using a binary collation?
>
Yes, the code:
class Mymodel(models.Model):
name = models.CharField(_('name'), max_length=50
On Wed, Aug 20, 2008 at 3:31 AM, anonymous <[EMAIL PROTECTED]> wrote:
>
> Hello all,
>
> I get the following error:
>
> In [2]: from myapp.models import *
>
> In [3]: Mymodel.objects.all()
> Out[3]:
> ---
> UnicodeDecodeE
* Szymon <[EMAIL PROTECTED]> [2008-04-30 07:34 -0700]:
>
> On 30 Kwi, 15:40, Amit Ramon <[EMAIL PROTECTED]> wrote:
> > Hope this helps,
>
> Yup. I've replaced that extra function with simple {{ foo.bar.0 }} in
> templates and now everything works, so that was problem you've
> described.
I still
On 30 Kwi, 15:40, Amit Ramon <[EMAIL PROTECTED]> wrote:
> Hope this helps,
Yup. I've replaced that extra function with simple {{ foo.bar.0 }} in
templates and now everything works, so that was problem you've
described.
Thank you very much! :)
Szymon
--~--~-~--~~~---~
* Szymon <[EMAIL PROTECTED]> [2008-04-30 01:43 -0700]:
>
> Hello,
>
> I have this code:
>
> foo = bar.objects.filter(status=True).extra(select={ 'litera' :
> 'LEFT(CONCAT(pseudonim, nazwisko), 1)' })
>
> and it gives me an error:
>
> 'utf8' codec can't decode byte 0xc5 in position 0: unexpect
Sorry, it was me being foolish. I created a query string that was utf-8 encoded
with non-ascii characters, and used it in a template anchor tag. It seems that
Firefox converts it according to RFC 2396 before sending it over, but IE leaves
it as is. request.get_full_path expects to receive an as
.96 is not unicode enabled, if you need to handle unicode strings you
will need to use SVN.
On Apr 23, 4:23 pm, "Boris Ozegovic" <[EMAIL PROTECTED]> wrote:
> On 4/23/08, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>
>
>
> > Are you using .96 or SVN?
>
> 0.96
--~--~-~--~~
On 4/23/08, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>
> Are you using .96 or SVN?
0.96
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-users@go
Are you using .96 or SVN?
On Apr 23, 3:56 pm, "Boris Ozegovic" <[EMAIL PROTECTED]> wrote:
> I am getting UnicodeDecodeError, 'ascii' codec can't decode byte 0xc4.
> I using utf-8 in forms.py, and also, my template is saved as UTF-8.
> And it doesn't work. Any ideas?
>
> This is part of my form
fizban wrote:
> On 12 Apr, 12:54, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote:
>> It sounds like you're using markdown 1.7. We haven't yet incorporated
>> the patch necessary to handle markdown 1.7 along with the earlier
>> versions. That will go in soon, though -- there's already a ticket in Tra
On 12 Apr, 17:06, Jens Diemer <[EMAIL PROTECTED]> wrote:
>
> btw. ticket:http://code.djangoproject.com/ticket/6387
Thanks, got the .diff
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post t
fizban schrieb:
> On 12 Apr, 12:54, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote:
>> It sounds like you're using markdown 1.7. We haven't yet incorporated
>> the patch necessary to handle markdown 1.7 along with the earlier
>> versions. That will go in soon, though -- there's already a ticket in T
On 12 Apr, 12:54, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote:
>
> It sounds like you're using markdown 1.7. We haven't yet incorporated
> the patch necessary to handle markdown 1.7 along with the earlier
> versions. That will go in soon, though -- there's already a ticket in Trac
> for it.
Ok,
On Sat, 2008-04-12 at 03:24 -0700, fizban wrote:
> I've fixed my issue by replacing smart_str with force_unicode in
> django.contrib.markup (the portion about markdown obviously).
>
> Why is django (latest svn trunk) passing bytestring to markdown, which
> is supposed to be fed by ascii or unico
I've fixed my issue by replacing smart_str with force_unicode in
django.contrib.markup (the portion about markdown obviously).
Why is django (latest svn trunk) passing bytestring to markdown, which
is supposed to be fed by ascii or unicode? :\
Should I fill a ticket or is there a valid reason to
> patrickk, I'm not sure what lapain's experience with unicode is, but
> please disregard the advice to switch defaultencoding to utf-8.
I didnt want this either, but some time you have to toil a bit for
debugging. I suggested him to use smart_str in post1, because i am
aware of recently merger o
I´ll do a django-update on the weekend.
If the problem still exists, I´ll post here again.
Thanks for the answers,
Patrick
On 29 Aug., 17:06, patrickk <[EMAIL PROTECTED]> wrote:
> I´m on revision 5646
>
> On 29 Aug., 16:57, "Jeremy Dunck" <[EMAIL PROTECTED]> wrote:
>
> > On 8/29/07, Michael Radz
I´m on revision 5646
On 29 Aug., 16:57, "Jeremy Dunck" <[EMAIL PROTECTED]> wrote:
> On 8/29/07, Michael Radziej <[EMAIL PROTECTED]> wrote:
>
>
>
>
>
> > On Wed, Aug 29, patrickk wrote:
>
> > > I just changed
> > > self._cache.set(key, value, timeout or self.default_timeout)
> > > to
> > > self._
On 8/29/07, Michael Radziej <[EMAIL PROTECTED]> wrote:
>
> On Wed, Aug 29, patrickk wrote:
>
> >
> > I just changed
> > self._cache.set(key, value, timeout or self.default_timeout)
> > to
> > self._cache.set(smart_str(key), value, timeout or
> > self.default_timeout)
> > in memcached.py
> > and it
On Wed, Aug 29, patrickk wrote:
>
> I just changed
> self._cache.set(key, value, timeout or self.default_timeout)
> to
> self._cache.set(smart_str(key), value, timeout or
> self.default_timeout)
> in memcached.py
> and it seems to work.
>
> Don´t know if that´s a proper solution though.
Me eit
I just changed
self._cache.set(key, value, timeout or self.default_timeout)
to
self._cache.set(smart_str(key), value, timeout or
self.default_timeout)
in memcached.py
and it seems to work.
Don´t know if that´s a proper solution though.
thanks,
patrick
On Aug 29, 10:32 am, Michael Radziej <[EMA
On Wed, Aug 29, patrickk wrote:
> instead of sending the whole stack, it´s probably easier to just check
> it yourself:
> http://skip.dedhost-sil-076.sil.at/trailer/
File "/usr/lib/python2.4/site-packages/memcache.py" in _set
328. fullcmd = "%s %s %d %d %d\r\n%s" % (cmd, key, flags, time, len
thanks jeremy.
here´s the information:
CACHE_BACKEND = 'memcached://dedhost-sil-076.sil.at:11211/'
I´m not using the cache_middleware, because I´m using the per-view-
cache. Just re-checked the django-docs and hope I don´t misunderstand
the whole caching-thing - but according to the docs, the
ca
On 8/28/07, patrickk <[EMAIL PROTECTED]> wrote:
>
> additional information:
> I just checked the default encoding
>
> >>> import sys
> >>> sys.getdefaultencoding()
> 'ascii'
>
> should that be something different (like utf-8)?
> btw: all our data (database) and scripts are encoded with utf-8.
pat
On 8/27/07, patrickk <[EMAIL PROTECTED]> wrote:
>
> With using the cache_page decorator, I´m getting a Unicode Error on my
> page:
>
> UnicodeDecodeError at /spezialprogramme/
> 'ascii' codec can't decode byte 0x80 in position 0: ordinal not in
> range(128)
>
patrickk, please give your whole stac
What middleware you are using .. any external middleware?
On Aug 28, 12:27 pm, patrickk <[EMAIL PROTECTED]> wrote:
> why prefer latin1 over utf-8 (in settings.py)?
>
> On 28 Aug., 09:12, Iapain <[EMAIL PROTECTED]> wrote:
>
> > > >>> import sys
> > > >>> sys.getdefaultencoding()
>
> > > 'ascii'
>
why prefer latin1 over utf-8 (in settings.py)?
On 28 Aug., 09:12, Iapain <[EMAIL PROTECTED]> wrote:
> > >>> import sys
> > >>> sys.getdefaultencoding()
>
> > 'ascii'
>
> Try using utf-8, btw it shouldnt be a problem. Lastly try using
> changing charset to latin1 in your settings.py .. I guess you
> >>> import sys
> >>> sys.getdefaultencoding()
>
> 'ascii'
Try using utf-8, btw it shouldnt be a problem. Lastly try using
changing charset to latin1 in your settings.py .. I guess your website
is not in english .. or it has some non-ascii char.
--~--~-~--~~~---~--~
additional information:
I just checked the default encoding
>>> import sys
>>> sys.getdefaultencoding()
'ascii'
should that be something different (like utf-8)?
btw: all our data (database) and scripts are encoded with utf-8.
thanks,
patrick
On 28 Aug., 08:21, patrickk <[EMAIL PROTECTED]> wrot
I´m sorry for bothering again, but our site has to be online soon and I
´m currently not able to use the cache_page decorator (which makes me
a bit nervous).
I did some research on smart_str, but I don´t know how and where to
use it and I also don´t see why this should solve the problem.
any feed
so you say I should use __str__ instead of __unicode__, right?
according to the django-docs, that´s not recommended though ...
On 27 Aug., 16:40, Iapain <[EMAIL PROTECTED]> wrote:
> > UnicodeDecodeError at /spezialprogramme/
> > 'ascii' codec can't decode byte 0x80 in position 0: ordinal not in
>
> UnicodeDecodeError at /spezialprogramme/
> 'ascii' codec can't decode byte 0x80 in position 0: ordinal not in
> range(128)
try using smart_str, it it doesnt work then use less restrictive decode
--~--~-~--~~~---~--~~
You received this message because you are su
On Sat, 2007-08-18 at 22:46 +, cesco wrote:
> Hi,
>
> I'm using sqlite3 as db for my django project.
> In order to load the data in the db I first generated a unicode string
> (which contains danish characters "ø, æ, å") and dumped such a string
> to a file (in json format) as follows:
> f_hd
Hi,
On 8/19/07, cesco <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> I'm using sqlite3 as db for my django project.
> In order to load the data in the db I first generated a unicode string
> (which contains danish characters "ø, æ, å") and dumped such a string
> to a file (in json format) as follows:
> f
On Fri, 2007-06-22 at 15:06 -0700, Boo wrote:
> Hi All.
> My form:
>
> class EditProfileForm(forms.Form):
> birthday =
> forms.DateField(widget=SelectDateWidget(years=range(1968, 1988)),
> label=_('Birthday'))
>
>
> If USE_I18N = True in settings, I receive an error:
>
> Request Method: GE
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 in
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 repor
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
> > instanc
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
.encod
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 can'
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 ca
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 wa
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 Gusta
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 0x
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. Add
97 matches
Mail list logo
