Tim Graham added the comment:
Here's an exception in Django after the latest patch. The Django code block in
the last exception catches ValueError, but this doesn't seem to work any longer
since it's "wrapped" in SystemError. As Berker mentioned, some upgrade tips
would be great as I'm not sure what adaptions in Django need to be made.
Traceback (most recent call last):
File "/home/tim/code/django/django/contrib/contenttypes/views.py", line 17,
in shortcut
content_type = ContentType.objects.get(pk=content_type_id)
File "/home/tim/code/django/django/db/models/manager.py", line 127, in
manager_method
return getattr(self.get_queryset(), name)(*args, **kwargs)
File "/home/tim/code/django/django/db/models/query.py", line 387, in get
self.model._meta.object_name
django.contrib.contenttypes.models.DoesNotExist: ContentType matching query
does not exist.
...
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
ValueError: could not convert string to float: request_path
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
....
File "/home/tim/code/django/django/template/base.py", line 792, in __init__
self.literal = float(var)
SystemError: <class 'ValueError'> returned a result with an error set
----------
nosy: +Tim.Graham
_______________________________________
Python tracker <[email protected]>
<http://bugs.python.org/issue23571>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
