Skip to content
Projects
Groups
Snippets
Help
This project
Loading...
Sign in / Register
Toggle navigation
D
django-rest-framework
Overview
Overview
Details
Activity
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Issues
0
Issues
0
List
Board
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Charts
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
edx
django-rest-framework
Commits
96f41fd1
Commit
96f41fd1
authored
Jun 27, 2013
by
Tom Christie
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Use imported views to expose python 2.6 bug. Refs #943
parent
4d22a65e
Show whitespace changes
Inline
Side-by-side
Showing
2 changed files
with
29 additions
and
23 deletions
+29
-23
rest_framework/tests/description.py
+26
-0
rest_framework/tests/test_description.py
+3
-23
No files found.
rest_framework/tests/description.py
0 → 100644
View file @
96f41fd1
# -- coding: utf-8 --
# Apparently there is a python 2.6 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.
from
rest_framework.views
import
APIView
# 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'
'Τη γλώσσα μου έδωσαν ελληνική'
'யாமறிந்த மொழிகளிலே தமிழ்மொழி'
'На берегу пустынных волн'
'てすと'
'アイウエオカキクケコサシスセソタチツテ'
)
class
ViewWithNonASCIICharactersInDocstring
(
APIView
):
__doc__
=
UTF8_TEST_DOCSTRING
rest_framework/tests/test_description.py
View file @
96f41fd1
...
@@ -2,8 +2,10 @@
...
@@ -2,8 +2,10 @@
from
__future__
import
unicode_literals
from
__future__
import
unicode_literals
from
django.test
import
TestCase
from
django.test
import
TestCase
from
rest_framework.views
import
APIView
from
rest_framework.compat
import
apply_markdown
,
smart_text
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
from
rest_framework.utils.formatting
import
get_view_name
,
get_view_description
# We check that docstrings get nicely un-indented.
# We check that docstrings get nicely un-indented.
...
@@ -49,28 +51,6 @@ MARKED_DOWN_gte_21 = """<h2 id="an-example-docstring">an example docstring</h2>
...
@@ -49,28 +51,6 @@ MARKED_DOWN_gte_21 = """<h2 id="an-example-docstring">an example docstring</h2>
<h2 id="hash-style-header">hash style header</h2>"""
<h2 id="hash-style-header">hash style header</h2>"""
# 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
):
class
TestViewNamesAndDescriptions
(
TestCase
):
def
test_view_name_uses_class_name
(
self
):
def
test_view_name_uses_class_name
(
self
):
"""
"""
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment