3 new commits in pytest:

https://bitbucket.org/hpk42/pytest/commits/fbad7df469fd/
Changeset:   fbad7df469fd
Branch:      jeffwidman/fix-faq-grammar-and-spelling-1423641159173
User:        jeffwidman
Date:        2015-02-11 07:52:48+00:00
Summary:     Fix: FAQ grammar and spelling
Affected #:  1 file

diff -r 46d5ac0ba396af887969a3cc9940fccba5ff1955 -r 
fbad7df469fd22f8f64367240983e5ecea92096f doc/en/faq.txt
--- a/doc/en/faq.txt
+++ b/doc/en/faq.txt
@@ -30,15 +30,15 @@
 If you are using trial's unittest.TestCase chances are that you can
 just run your tests even if you return Deferreds.  In addition,
 there also is a dedicated `pytest-twisted
-<http://pypi.python.org/pypi/pytest-twisted>`_ plugin which allows to
-return deferreds from pytest-style tests, allowing to use
+<http://pypi.python.org/pypi/pytest-twisted>`_ plugin which allows you to
+return deferreds from pytest-style tests, allowing the use of
 :ref:`fixtures` and other features.
 
 how does pytest work with Django?
 ++++++++++++++++++++++++++++++++++++++++++++++
 
 In 2012, some work is going into the `pytest-django plugin 
<http://pypi.python.org/pypi/pytest-django>`_.  It substitutes the usage of 
Django's
-``manage.py test`` and allows to use all pytest features_ most of which
+``manage.py test`` and allows the use of all pytest features_ most of which
 are not available from Django directly.
 
 .. _features: features.html
@@ -49,7 +49,7 @@
 
 Around 2007 (version ``0.8``) some people thought that ``pytest``
 was using too much "magic".  It had been part of the `pylib`_ which
-contains a lot of unreleated python library code.  Around 2010 there
+contains a lot of unrelated python library code.  Around 2010 there
 was a major cleanup refactoring, which removed unused or deprecated code
 and resulted in the new ``pytest`` PyPI package which strictly contains
 only test-related code.  This release also brought a complete pluginification
@@ -63,7 +63,7 @@
 Nowadays, ``pytest`` explicitely rewrites assert statements in test modules
 in order to provide more useful :ref:`assert feedback <assertfeedback>`.
 This completely avoids previous issues of confusing assertion-reporting.
-It also means, that you can use Python's ``-O`` optimization without loosing
+It also means, that you can use Python's ``-O`` optimization without losing
 assertions in test modules.
 
 ``pytest`` contains a second, mostly obsolete, assert debugging technique,
@@ -105,7 +105,7 @@
 
 For simple applications and for people experienced with nose_ or
 unittest-style test setup using `xUnit style setup`_ probably
-feels natural.  For larger test suites, parametrized testing
+feels natural.  For larger test suites, parameterized testing
 or setup of complex test resources using funcargs_ may feel more natural.
 Moreover, funcargs are ideal for writing advanced test support
 code (like e.g. the monkeypatch_, the tmpdir_ or capture_ funcargs)
@@ -152,13 +152,13 @@
 Issues with pytest, multiprocess and setuptools?
 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++
 
-On windows the multiprocess package will instantiate sub processes
+On Windows the multiprocess package will instantiate sub processes
 by pickling and thus implicitly re-import a lot of local modules.
 Unfortunately, setuptools-0.6.11 does not ``if __name__=='__main__'``
 protect its generated command line script.  This leads to infinite
 recursion when running a test that instantiates Processes.
 
-As of middle 2013, there shouldn't be a problem anymore when you
+As of mid-2013, there shouldn't be a problem anymore when you
 use the standard setuptools (note that distribute has been merged
 back into setuptools which is now shipped directly with virtualenv).
 


https://bitbucket.org/hpk42/pytest/commits/d91185b2447f/
Changeset:   d91185b2447f
Branch:      jeffwidman/fix-faq-grammar-and-spelling-1423641159173
User:        jeffwidman
Date:        2015-02-11 19:27:51+00:00
Summary:     Changed back to "parametrized" to match the API
Affected #:  1 file

diff -r fbad7df469fd22f8f64367240983e5ecea92096f -r 
d91185b2447f9baddd521690f4fb460c2fb70b3b doc/en/faq.txt
--- a/doc/en/faq.txt
+++ b/doc/en/faq.txt
@@ -105,7 +105,7 @@
 
 For simple applications and for people experienced with nose_ or
 unittest-style test setup using `xUnit style setup`_ probably
-feels natural.  For larger test suites, parameterized testing
+feels natural.  For larger test suites, parametrized testing
 or setup of complex test resources using funcargs_ may feel more natural.
 Moreover, funcargs are ideal for writing advanced test support
 code (like e.g. the monkeypatch_, the tmpdir_ or capture_ funcargs)


https://bitbucket.org/hpk42/pytest/commits/5fc366c50b56/
Changeset:   5fc366c50b56
User:        flub
Date:        2015-02-12 09:32:32+00:00
Summary:     Merged in 
jeffwidman/pytest/jeffwidman/fix-faq-grammar-and-spelling-1423641159173 (pull 
request #246)

Fix FAQ grammar and spelling
Affected #:  1 file

diff -r 46d5ac0ba396af887969a3cc9940fccba5ff1955 -r 
5fc366c50b56a94638c959be8456d2cb3c7e7c1c doc/en/faq.txt
--- a/doc/en/faq.txt
+++ b/doc/en/faq.txt
@@ -30,15 +30,15 @@
 If you are using trial's unittest.TestCase chances are that you can
 just run your tests even if you return Deferreds.  In addition,
 there also is a dedicated `pytest-twisted
-<http://pypi.python.org/pypi/pytest-twisted>`_ plugin which allows to
-return deferreds from pytest-style tests, allowing to use
+<http://pypi.python.org/pypi/pytest-twisted>`_ plugin which allows you to
+return deferreds from pytest-style tests, allowing the use of
 :ref:`fixtures` and other features.
 
 how does pytest work with Django?
 ++++++++++++++++++++++++++++++++++++++++++++++
 
 In 2012, some work is going into the `pytest-django plugin 
<http://pypi.python.org/pypi/pytest-django>`_.  It substitutes the usage of 
Django's
-``manage.py test`` and allows to use all pytest features_ most of which
+``manage.py test`` and allows the use of all pytest features_ most of which
 are not available from Django directly.
 
 .. _features: features.html
@@ -49,7 +49,7 @@
 
 Around 2007 (version ``0.8``) some people thought that ``pytest``
 was using too much "magic".  It had been part of the `pylib`_ which
-contains a lot of unreleated python library code.  Around 2010 there
+contains a lot of unrelated python library code.  Around 2010 there
 was a major cleanup refactoring, which removed unused or deprecated code
 and resulted in the new ``pytest`` PyPI package which strictly contains
 only test-related code.  This release also brought a complete pluginification
@@ -63,7 +63,7 @@
 Nowadays, ``pytest`` explicitely rewrites assert statements in test modules
 in order to provide more useful :ref:`assert feedback <assertfeedback>`.
 This completely avoids previous issues of confusing assertion-reporting.
-It also means, that you can use Python's ``-O`` optimization without loosing
+It also means, that you can use Python's ``-O`` optimization without losing
 assertions in test modules.
 
 ``pytest`` contains a second, mostly obsolete, assert debugging technique,
@@ -152,13 +152,13 @@
 Issues with pytest, multiprocess and setuptools?
 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++
 
-On windows the multiprocess package will instantiate sub processes
+On Windows the multiprocess package will instantiate sub processes
 by pickling and thus implicitly re-import a lot of local modules.
 Unfortunately, setuptools-0.6.11 does not ``if __name__=='__main__'``
 protect its generated command line script.  This leads to infinite
 recursion when running a test that instantiates Processes.
 
-As of middle 2013, there shouldn't be a problem anymore when you
+As of mid-2013, there shouldn't be a problem anymore when you
 use the standard setuptools (note that distribute has been merged
 back into setuptools which is now shipped directly with virtualenv).

Repository URL: https://bitbucket.org/hpk42/pytest/

--

This is a commit notification from bitbucket.org. You are receiving
this because you have the service enabled, addressing the recipient of
this email.
_______________________________________________
pytest-commit mailing list
pytest-commit@python.org
https://mail.python.org/mailman/listinfo/pytest-commit

Reply via email to