From 96f41fd12d376833a5822918cedcec5e74d59d02 Mon Sep 17 00:00:00 2001
From: Tom Christie
Date: Thu, 27 Jun 2013 11:58:34 +0100
Subject: Use imported views to expose python 2.6 bug. Refs #943
---
rest_framework/tests/test_description.py | 26 +++-----------------------
1 file changed, 3 insertions(+), 23 deletions(-)
(limited to 'rest_framework/tests/test_description.py')
diff --git a/rest_framework/tests/test_description.py b/rest_framework/tests/test_description.py
index ea4b2c3a..8019f5ec 100644
--- a/rest_framework/tests/test_description.py
+++ b/rest_framework/tests/test_description.py
@@ -2,8 +2,10 @@
from __future__ import unicode_literals
from django.test import TestCase
-from rest_framework.views import APIView
from rest_framework.compat import apply_markdown, smart_text
+from rest_framework.views import APIView
+from rest_framework.tests.description import ViewWithNonASCIICharactersInDocstring
+from rest_framework.tests.description import UTF8_TEST_DOCSTRING
from rest_framework.utils.formatting import get_view_name, get_view_description
# We check that docstrings get nicely un-indented.
@@ -49,28 +51,6 @@ MARKED_DOWN_gte_21 = """an example docstring
"""
-# test strings snatched from http://www.columbia.edu/~fdc/utf8/,
-# http://winrus.com/utf8-jap.htm and memory
-UTF8_TEST_DOCSTRING = (
- 'zażółć gęślą jaźń'
- 'Sîne klâwen durh die wolken sint geslagen'
- 'Τη γλώσσα μου έδωσαν ελληνική'
- 'யாமறிந்த மொழிகளிலே தமிழ்மொழி'
- 'На берегу пустынных волн'
- 'てすと'
- 'ｱｲｳｴｵｶｷｸｹｺｻｼｽｾｿﾀﾁﾂﾃ'
-)
-
-
-# Apparently there is an issue where docstrings of imported view classes
-# do not retain their encoding information even if a module has a proper
-# encoding declaration at the top of its source file. Therefore for tests
-# to catch unicode related errors, a mock view has to be declared in a separate
-# module.
-class ViewWithNonASCIICharactersInDocstring(APIView):
- __doc__ = UTF8_TEST_DOCSTRING
-
-
class TestViewNamesAndDescriptions(TestCase):
def test_view_name_uses_class_name(self):
"""
--
cgit v1.2.3