Re: urllib.urlencode wrongly encoding � character

2006-04-07 Thread Fredrik Lundh
Evren Esat Ozkan wrote: > Ok, I think this code snippet enough to show what i said; > > === > > #!/usr/bin/env python > # -*- coding: utf-8 -*- > #Change utf-8 to latin-1 > #Or move variable decleration to another file than import it > > val='00090±NO:±H±H±H±H

Re: urllib.urlencode wrongly encoding � character

2006-04-06 Thread Fredrik Lundh
Evren Esat Ozkan wrote: > when I remove "# -*- coding: utf-8 -*-" line from start of the script > it worked properly. So I moved variable decleration to another file and > imported than it worked too. the coding directive controls how *unicode* literals in the *source code* are parsed into unic

Re: urllib.urlencode wrongly encoding � character

2006-04-06 Thread Richard Brodie
"Fredrik Lundh" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > I'm obviously missing some context here, but "encoding ± to %B1 on any > platform" is exactly what urlencode does: > >>>> import urllib >>>> urllib.urlencode([("key", chr(0xb1))]) >'key=%B1' Yeah but you'

Re: urllib.urlencode wrongly encoding � character

2006-04-06 Thread Fredrik Lundh
[EMAIL PROTECTED] wrote: > I think there should be way to encode ± to %B1 on any platform/locale > combination. While searching for a real solution, I'm going to add a > search&destroy filter for %C2 on urlencoded dictionary as a workaround. > Because my queries are constant and %C2 is the only p