#18692: Django 1.3.2 breaks Python 2.4 compatibility
-------------------------------+--------------------
Reporter: chipx86 | Owner: nobody
Type: Bug | Status: new
Component: HTTP handling | Version: 1.3
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+--------------------
The recent URL scheme restriction change assumes Python 2.5+ accessors for
the parsed URI information. Specifically, it's looking up parsed.scheme,
which isn't available in Python 2.4. Instead, it should be accessing it as
a tuple.
The traceback below shows what's happening.
{{{
Traceback (most recent call last):
File "/usr/lib/python2.4/site-
packages/Django-1.3.2-py2.4.egg/django/core/handlers/base.py", line 111,
in get_response
response = callback(request, *callback_args, **callback_kwargs)
File "/usr/lib/python2.4/site-
packages/Django-1.3.2-py2.4.egg/django/views/generic/simple.py", line 57,
in redirect_to
return klass(url % kwargs)
File "/usr/lib/python2.4/site-
packages/Django-1.3.2-py2.4.egg/django/http/__init__.py", line 645, in
__init__
if parsed.scheme and parsed.scheme not in self.allowed_schemes:
AttributeError: 'tuple' object has no attribute 'scheme'
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/18692>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit https://groups.google.com/groups/opt_out.
