root
/
flask
mirror of https://github.com/pallets/flask.git
1
0
Fork 0
Code Issues Actions 1 Packages Projects Releases Wiki Activity

Unify the uses of "testsuite" vs "test suite". 

Use "test suite", which is more prevailing in the source code.
This commit is contained in:
Petr Zemek 2014-10-27 11:31:01 +01:00
parent ec3d5800f2
commit ebab6718f7
4 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
CHANGES
View File

@ -49,7 +49,7 @@ Version 1.0
users debug when the wrong templates are loaded. users debug when the wrong templates are loaded.
- Enforce blueprint handling in the order they were registered for template - Enforce blueprint handling in the order they were registered for template
loading. loading.
- Ported testsuite to py.test. - Ported test suite to py.test.
- Deprecated ``request.json`` in favour of ``request.get_json()``. - Deprecated ``request.json`` in favour of ``request.get_json()``.
- Add "pretty" and "compressed" separators definitions in jsonify() method. - Add "pretty" and "compressed" separators definitions in jsonify() method.
Reduces JSON response size when JSONIFY_PRETTYPRINT_REGULAR=False by removing Reduces JSON response size when JSONIFY_PRETTYPRINT_REGULAR=False by removing

2
docs/patterns/fabric.rst
View File

@ -186,7 +186,7 @@ deployment actually fun:
out the latest version on the server and then install. That way you out the latest version on the server and then install. That way you
can also easily go back to older versions. can also easily go back to older versions.
- hook in testing functionality so that you can deploy to an external - hook in testing functionality so that you can deploy to an external
server and run the testsuite. server and run the test suite.
Working with Fabric is fun and you will notice that it's quite magical to Working with Fabric is fun and you will notice that it's quite magical to
type ``fab deploy`` and see your application being deployed automatically type ``fab deploy`` and see your application being deployed automatically

2
docs/upgrading.rst
View File

@ -96,7 +96,7 @@ as `ValueError` you will need to change this.
Due to a bug in the test client Flask 0.7 did not trigger teardown Due to a bug in the test client Flask 0.7 did not trigger teardown
handlers when the test client was used in a with statement. This was handlers when the test client was used in a with statement. This was
since fixed but might require some changes in your testsuites if you since fixed but might require some changes in your test suites if you
relied on this behavior. relied on this behavior.
Version 0.7 Version 0.7

2
flask/ctx.py
View File

@ -291,7 +291,7 @@ class RequestContext(object):
# information under debug situations. However if someone forgets to # information under debug situations. However if someone forgets to
# pop that context again we want to make sure that on the next push # pop that context again we want to make sure that on the next push
# it's invalidated, otherwise we run at risk that something leaks # it's invalidated, otherwise we run at risk that something leaks
# memory. This is usually only a problem in testsuite since this # memory. This is usually only a problem in test suite since this
# functionality is not active in production environments. # functionality is not active in production environments.
top = _request_ctx_stack.top top = _request_ctx_stack.top
if top is not None and top.preserved: if top is not None and top.preserved: