I can't explain the additional space, but URL-encoding a Unicode string
isn't generally possible, it needs to be encoded first. UTF-8 is almost
always the correct encoding to use, so in your case:
qk = quote(query_text.encode('utf8'))
Anything you can do to avoid having to include text like th
Hi - I'm not sure if this is a Django problem, but I'm working on a Django
project so I thought I'd start here.
In my project users will submit text by way of a text field which will
eventually be encoded with urllib.quote() and used in a url. When I submit
text, certain characters appear on m
Hi,
On 19.03.2009, at 11:02, Juan Hernandez wrote:
> Hi there,
>
> This has been killing me for hours and I don't know what else to do.
> Is about the famous charset in django.
>
> I have this model:
>
> class Post(models.Model):
> user = models.ForeignKey(User)
> category = models.Fore
Hi.
I'm not sure what exactly you are doing and how/where you are
displaying this stuff. But it sounds like you are escaping the html,
django does this by default to protect sites from XSS attacks ect. You
can either stop the auto escaping in the template or use the |safe
tag. You can read about d
On Wed, Mar 18, 2009 at 11:32 AM, Juan Hernandez wrote:
> Hi there,
>
> This has been killing me for hours and I don't know what else to do. Is
> about the famous charset in django.
>
> I have this model:
>
> class Post(models.Model):
> user = models.ForeignKey(User)
> category = models.Fo
Hi there,
This has been killing me for hours and I don't know what else to do. Is
about the famous charset in django.
I have this model:
class Post(models.Model):
user = models.ForeignKey(User)
category = models.ForeignKey(Categories)
title = models.CharField(max_length=50)
post
On Mon, 2007-08-20 at 17:27 +, arthur debert wrote:
> Hi Rob.
>
> After the unicode branch merge django expects and produces unicodes
> objects throughout.
>
> A detail how to port guide is here:
> http://code.djangoproject.com/wiki/UnicodeBranch#PortingApplicationsTheQuickChecklist
>
> In
Hi Rob.
After the unicode branch merge django expects and produces unicodes
objects throughout.
A detail how to port guide is here:
http://code.djangoproject.com/wiki/UnicodeBranch#PortingApplicationsTheQuickChecklist
In this specific case, you can call "lower" directly on your unicode
object:
After moving to the latest version of Django one of the functions I
wrote fails to work.
I'll drop the code...
def year_cal(sectie, req_year = None, req_month=None):
cur_year= str(datetime.datetime.now().year)
cur_month= datetime.datetime.now().strftime("%b")
all_month_list = ['jan', 'fe
9 matches
Mail list logo
