Changes between Version 6 and Version 7 of Ticket #21198, comment 2
- Timestamp:
- Sep 30, 2013, 8:34:22 AM (11 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #21198, comment 2
v6 v7 1 Thanks for the link, but I don't get why that would work on Django 1.4.2 and not on Django 1.5.4.1 Thanks for the link, also, it seems like the error is the same in both 1.4.2 and 1.5.4, sorry for the false alarm. 2 2 3 Itkinds of look like the user should use `@python_2_unicode_compatible` on any model class that is "Python2-unicode-compatible", even by inheritance.3 Anyway, it does kinds of look like the user should use `@python_2_unicode_compatible` on any model class that is "Python2-unicode-compatible", even by inheritance. 4 4 5 So maybe it would be cool to raise a specific exception if `@python_2_unicode_compatible` is applied on a class without an `__str__` method indeed. 5 So maybe it would be cool to raise a specific exception if `@python_2_unicode_compatible` is applied on a class without an `__str__` method indeed. That would avoid the need of checking the documentation for the user :D