Well, either way, thank you so much for helping me on this. The more I dive into the framework and more so, Python, the more I know i've made the right choice.
John On May 29, 11:15 am, "Karen Tracey" <[EMAIL PROTECTED]> wrote: > On Thu, May 29, 2008 at 1:16 PM, John M <[EMAIL PROTECTED]> wrote: > > Ill give that a try, but seems like I'm working against the framework > > doesn't it? > > Nah, working against the framework would be rooting around in undocumented > internal data structures to get the data you are looking for. > HttpRequest.META['QUERY_STRING'] is documented > (http://www.djangoproject.com/documentation/request_response/#attributes) and > the rest is just standard Python library code. > > > I could swear I was able to set the encoding, GET the fields I wanted > > and then do it another way, but I need to move on in my coding, I hope > > this works. > > There may be some way to un-do the unicodification but it isn't obvious to > me. Fact is you don't want this query parameter turned into unicode, you > want he hex representation of what's essentially a byte string, represented > in the url as a mix of ASCII and percent-encoded octets. For that I think > it is more straightforward to start with the raw query string vs. attempting > to reverse what the framework did in constructing the request.GET > dictionary. But that's just my opinion, of course. > > Karen --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
