Re: [Django] #9859: UnicodeDecodeError in admin views for python 2.3.

[Django]

#9859: UnicodeDecodeError in admin views for python 2.3.
---+
  Reporter:  nfg   | Owner:  kmtracey   
   
Status:  assigned  | Milestone: 
   
 Component:  django.contrib.admin  |   Version:  SVN
   
Resolution:|  Keywords:  unicode 
unicodedecodeerror
 Stage:  Accepted  | Has_patch:  1  
   
Needs_docs:  0 |   Needs_tests:  0  
   
Needs_better_patch:  0 |  
---+
Changes (by kmtracey):

  * status:  new => assigned
  * needs_better_patch:  => 0
  * needs_tests:  => 0
  * owner:  nobody => kmtracey
  * needs_docs:  => 0
  * stage:  Unreviewed => Accepted

Comment:

 Thanks for the report, fix, and test.  Does your company have plans to
 upgrade to a higher level of Python?  Django will be dropping Python 2.3
 support at some point, though I'm not sure if it's been finally decided
 exactly when yet.

-- 
Ticket URL: 
Django 
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 django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

[Django] #9859: UnicodeDecodeError in admin views for python 2.3.

[Django]

#9859: UnicodeDecodeError in admin views for python 2.3.
+---
 Reporter:  nfg |   Owner:  nobody
   Status:  new |   Milestone:
Component:  django.contrib.admin| Version:  SVN   
 Keywords:  unicode unicodedecodeerror  |   Stage:  Unreviewed
Has_patch:  1   |  
+---
 Because I work in a company that uses python 2.3 on the production server
 and because I use characters outside the ascii range, I have run onto a
 number of UnicodeDecodeErrors. Python 2.3 unfortunately has a bug, it
 calls __str__ methods on objects included in unicode template strings even
 if the object has a __unicode__ method.

 Now I have run onto another one. It was a quick fix to solve this, but it
 was more difficult to make a regression test for it. This bug is only
 triggered if a model is registered as a inline, but not registered
 directly with the admin.

 To help fight UnicodeDecodeErrors I have made a new TestCase class in the
 admin_views regression test with the sole purpose of detecting missing
 force_unicode calls in the admin views.

-- 
Ticket URL: 
Django 
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 django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---