Comment redirect breaks if you want to send get data

[Nate]

I'm making a site where you can view models in sets, and the sets are specified with GET. So you may have a url like /entries/?set=first or something. With the django comment system, you can have the form redirect by setting "next" in a hidden field or the like, and the comment form redirects there when it's done. However, it sends get data of its own, and assumes that the url in "next" doesn't already have get data. In my case it does. Thus, django comments just sticks "?c=whatever" on the end of my url, which is wrong. I've supplied a patch that simply checks if the url has GET data (I just search for ".*?[^{/]*$", which is probably horribly wrong, but it works for my intents and purposes), and if that matches, comments uses "&" instead of "?".}

[Thejaswi Puthraya]

Your problem seems genuine, but can you please follow the coding style
adopted in django.

• No imports within a function
• I doubt if the

    'a' if something else 'b'
  

  works with Python-2.4 and earlier.

[Chris Beaven]

Fixed in r10424