New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

pdb: resume capturing after `continue` #2619

Merged
merged 2 commits into from Oct 25, 2018

Conversation

Projects
None yet
4 participants
@blueyed
Contributor

blueyed commented Jul 26, 2017

After pdb.set_trace() capturing is turned off.
This patch resumes it after using the continue (or c / cont)
command.

I've noticed that any captured output from before the set_trace is lost, but that does not appear to be caused by my patch - need to investigate.
I've only tested this on master for now.

TODO:

  • Add a new news fragment into the changelog folder
    • name it $issue_id.$type for example (588.bug)
    • if you don't have an issue_id change it to the pr id after creating the pr
    • ensure type is one of removal, feature, bugfix, vendor, doc or trivial
    • Make sure to use full sentences with correct case and punctuation, for example: "Fix issue with non-ascii contents in doctest text files."
  • Target: for bugfix, vendor, doc or trivial fixes, target master; for removals or features target features;
  • Make sure to include reasonable tests for your change if necessary
@blueyed

This comment has been minimized.

Contributor

blueyed commented Jul 26, 2017

I've noticed that any captured output from before the set_trace is lost

That is: when using import pdb; pdb.set_trace in a test, any stderr/stdout before that gets not displayed by pytest in case the test fails later.
It can be seen when using pytest -s, so it should also be captured (and kept) before set_trace is used.

@coveralls

This comment has been minimized.

coveralls commented Jul 26, 2017

Coverage Status

Coverage decreased (-0.1%) to 91.789% when pulling ff89643 on blueyed:pdb-resume-capture into 309152d on pytest-dev:features.

@RonnyPfannschmidt

at first glance this looks good, is there a easy way t make a automated test for this using pexpect in pytester?

@blueyed

This comment has been minimized.

Contributor

blueyed commented Jul 26, 2017

Thanks.
Pushed a fixup for also hooking into setup.
Don't know about a test..

Regarding the other issue (capturing being lost), I've noticed that Django's reverse (loading the apps / setting up Django) changes the root logger's handlers:

From [<StreamHandler <_io.FileIO name=9 mode='rb+' closefd=True> (INFO)>, <LogCaptureHandler (NOTSET)>] to [<StreamHandler <stderr> (INFO)>].

(via logging.getLogger().handlers)
So this is not a pytest issue probably.

@coveralls

This comment has been minimized.

coveralls commented Jul 26, 2017

Coverage Status

Coverage decreased (-0.03%) to 93.752% when pulling fd29c57 on blueyed:pdb-resume-capture into b394066 on pytest-dev:features.

@blueyed

This comment has been minimized.

Contributor

blueyed commented Jul 26, 2017

Only py27-pexpect failed, but not py35-pexpect?!

@nicoddemus

This comment has been minimized.

Member

nicoddemus commented Jul 26, 2017

Hmm I'm under the impression that those "pexpect" tests are flaky; had to restart a single failing job today which passed the second time.

Restarted your py27-pexpect a now other tests failed.

@nicoddemus

This comment has been minimized.

Member

nicoddemus commented Nov 10, 2017

@blueyed gentle ping. 👍

@blueyed

This comment has been minimized.

Contributor

blueyed commented Mar 27, 2018

Rebased and fixed/adjusted.

There are two failures with py27-pexpect that need investigation:

FAIL test_pdb.py::TestPDB::()::test_pdb_interaction_capturing_simple
FAIL test_pdb.py::TestPDB::()::test_pdb_interaction_capturing_twice

@blueyed

This comment has been minimized.

Contributor

blueyed commented Mar 27, 2018

What about a new pytest_leave_pdb hook (to complement pytest_enter_pdb)?

@RonnyPfannschmidt

This comment has been minimized.

Member

RonnyPfannschmidt commented Mar 27, 2018

why is the hook not actually pytest_enter_pdb(config, frame), so thecapture plugin could implement a hookwrapper

i would like to propose a pytest_debug(hook) that allows integration of general debuggers

@blueyed

This comment has been minimized.

Contributor

blueyed commented Mar 27, 2018

@RonnyPfannschmidt

  1. So you are suggesting to add frame to the existing hook, and use it internally?
  2. I do not understand fully how pytest_debug(hook) would work.

Both points appear to be outside the scope of this PR though, but we can create new issues/PRs for them, of course.

@RonnyPfannschmidt

This comment has been minimized.

Member

RonnyPfannschmidt commented Mar 28, 2018

sorry my mistake, i meant to write pytest_debug(config, frame)

@blueyed

This comment has been minimized.

Contributor

blueyed commented Mar 28, 2018

So instead of pytest_enter_pdb could be kept as-is, but pytest_debug added (without adding pytest_leave_pdb then)?

@RonnyPfannschmidt

This comment has been minimized.

Member

RonnyPfannschmidt commented Mar 28, 2018

@blueyed correct

@nicoddemus

This comment has been minimized.

Member

nicoddemus commented May 3, 2018

Hey guys gentle ping. 😁

@nicoddemus

This comment has been minimized.

Member

nicoddemus commented Aug 26, 2018

It seems there is still tests failing... 😕

@blueyed

This comment has been minimized.

Contributor

blueyed commented Aug 29, 2018

Yeah, py27-pexpect still / again(?) failing like before.

@codecov

This comment has been minimized.

codecov bot commented Sep 19, 2018

Codecov Report

Merging #2619 into features will increase coverage by 1.11%.
The diff coverage is 65.85%.

Impacted file tree graph

@@             Coverage Diff              @@
##           features    #2619      +/-   ##
============================================
+ Coverage     94.66%   95.77%   +1.11%     
============================================
  Files           109      109              
  Lines         24308    24344      +36     
  Branches       2398     2403       +5     
============================================
+ Hits          23010    23315     +305     
+ Misses          990      733     -257     
+ Partials        308      296      -12
Flag Coverage Δ
#docs 28.46% <4.87%> (-0.05%) ⬇️
#doctesting 28.46% <4.87%> (-0.05%) ⬇️
#linting 28.46% <4.87%> (-0.05%) ⬇️
#linux 95.55% <65.85%> (+1.85%) ⬆️
#nobyte 91.74% <7.31%> (+0.46%) ⬆️
#numpy 92.87% <65.85%> (+0.98%) ⬆️
#pexpect 41.31% <65.85%> (?)
#py27 93.91% <65.85%> (+1.45%) ⬆️
#py34 92.12% <7.31%> (-0.06%) ⬇️
#py35 92.13% <7.31%> (+0.57%) ⬆️
#py36 93.86% <65.85%> (+0.91%) ⬆️
#py37 92.19% <29.26%> (?)
#trial 92.87% <65.85%> (+0.98%) ⬆️
#windows 93.89% <7.31%> (-0.13%) ⬇️
#xdist 93.63% <7.31%> (+0.37%) ⬆️
Impacted Files Coverage Δ
testing/test_pdb.py 95.06% <100%> (+51.21%) ⬆️
src/_pytest/hookspec.py 100% <100%> (ø) ⬆️
src/_pytest/debugging.py 86.09% <41.66%> (+25.62%) ⬆️
testing/code/test_code.py 94.11% <0%> (-1.34%) ⬇️
src/_pytest/config/__init__.py 94.92% <0%> (-0.03%) ⬇️
testing/code/test_source.py 97.02% <0%> (ø) ⬆️
src/_pytest/assertion/rewrite.py 95.68% <0%> (+0.16%) ⬆️
src/_pytest/pytester.py 87.3% <0%> (+0.72%) ⬆️
testing/test_terminal.py 100% <0%> (+0.78%) ⬆️
src/_pytest/helpconfig.py 99.06% <0%> (+1.86%) ⬆️
... and 6 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 65b97c2...ede3a4e. Read the comment docs.

@blueyed blueyed changed the title from pdb: resume capturing after `continue` to [WIP] pdb: resume capturing after `continue` Oct 11, 2018

@nicoddemus

We need a new changelog entry before merging this.

@blueyed

This comment has been minimized.

Contributor

blueyed commented Oct 12, 2018

@nicoddemus
Ok.
It also needs to be fixed (tests), and I need to review it myself - I am just rebasing it from time to time to see if tests might pass etc.. ;)

@nicoddemus

This comment has been minimized.

Member

nicoddemus commented Oct 12, 2018

Sure thing, thanks! 😁

@blueyed blueyed changed the title from [WIP] pdb: resume capturing after `continue` to pdb: resume capturing after `continue` Oct 23, 2018

@blueyed blueyed requested review from RonnyPfannschmidt and nicoddemus Oct 23, 2018

@blueyed

This comment has been minimized.

Contributor

blueyed commented Oct 23, 2018

This should be ready now.

I have a followup to also handle quit with pdb.set_trace(), but that is a new feature/bugfix, so I will submit it later.

@@ -609,3 +609,13 @@ def pytest_enter_pdb(config):
:param _pytest.config.Config config: pytest config object
"""
def pytest_leave_pdb(config):

This comment has been minimized.

@RonnyPfannschmidt

RonnyPfannschmidt Oct 24, 2018

Member

would it make sense to add the actual debugger as argument here?

This comment has been minimized.

@blueyed

blueyed Oct 24, 2018

Contributor

Good idea.
I'll add a new arg pdb.
The same might make sense for pytest_enter_pdb then maybe also?!

This comment has been minimized.

@nicoddemus

nicoddemus Oct 24, 2018

Member

Agree to both points. 👍

@@ -609,3 +609,13 @@ def pytest_enter_pdb(config):
:param _pytest.config.Config config: pytest config object
"""
def pytest_leave_pdb(config):

This comment has been minimized.

@nicoddemus

nicoddemus Oct 24, 2018

Member

Agree to both points. 👍

Added the pdb arg to the hooks.

@nicoddemus

This comment has been minimized.

Member

nicoddemus commented Oct 24, 2018

Hmm we got a crash on py36-xdist:

_________________________ testing/code/test_excinfo.py _________________________
[gw0] linux -- Python 3.6.3 /home/travis/build/pytest-dev/pytest/.tox/py36-xdist/bin/python
Worker 'gw0' crashed while running 'testing/code/test_excinfo.py::TestFormattedExcinfo::()::test_repr_traceback_recursion'

I will restart that job to see if it is a flaky test.

@nicoddemus

This comment has been minimized.

Member

nicoddemus commented Oct 24, 2018

Hmm it passed when ran again. Let's keep an eye on this to find out if it was a fluke or actually a flaky test.

blueyed added some commits Jul 26, 2017

pdb: resume capturing after `continue`
After `pdb.set_trace()` capturing is turned off.
This patch resumes it after using the `continue` (or `c` / `cont`)
command.

Store _pytest_capman on the class, for pdbpp's do_debug hack to keep it.

Without this, `debug …` would fail like this:

    /usr/lib/python3.6/cmd.py:217: in onecmd
        return func(arg)
    .venv/lib/python3.6/site-packages/pdb.py:608: in do_debug
        return orig_do_debug(self, arg)
    /usr/lib/python3.6/pdb.py:1099: in do_debug
        sys.call_tracing(p.run, (arg, globals, locals))
    /usr/lib/python3.6/bdb.py:434: in run
        exec(cmd, globals, locals)
    /usr/lib/python3.6/bdb.py:51: in trace_dispatch
        return self.dispatch_line(frame)
    /usr/lib/python3.6/bdb.py:69: in dispatch_line
        self.user_line(frame)
    /usr/lib/python3.6/pdb.py:261: in user_line
        self.interaction(frame, None)
    .venv/lib/python3.6/site-packages/pdb.py:203: in interaction
        self.setup(frame, traceback)
    E   AttributeError: 'PytestPdb' object has no attribute '_pytest_capman'

- add pytest_leave_pdb hook
- fixes test_pdb_interaction_capturing_twice: would fail on master now,
  but works here

@blueyed blueyed merged commit f466105 into pytest-dev:features Oct 25, 2018

1 of 2 checks passed

continuous-integration/appveyor/pr Waiting for AppVeyor build to complete
Details
continuous-integration/travis-ci/pr The Travis CI build passed
Details

@blueyed blueyed deleted the blueyed:pdb-resume-capture branch Oct 25, 2018

peterbe added a commit to mozilla-services/tecken that referenced this pull request Nov 5, 2018

Update pytest to 3.10.0 (#1292)
This PR updates [pytest](https://pypi.org/project/pytest) from **3.9.3** to **3.10.0**.



<details>
  <summary>Changelog</summary>
  
  
   ### 3.10.0
   ```
   ==========================

Features
--------

- `2619 &lt;https://github.com/pytest-dev/pytest/issues/2619&gt;`_: Resume capturing output after ``continue`` with ``__import__(&quot;pdb&quot;).set_trace()``.

  This also adds a new ``pytest_leave_pdb`` hook, and passes in ``pdb`` to the
  existing ``pytest_enter_pdb`` hook.


- `4147 &lt;https://github.com/pytest-dev/pytest/issues/4147&gt;`_: Add ``-sw``, ``--stepwise`` as an alternative to ``--lf -x`` for stopping at the first failure, but starting the next test invocation from that test.  See `the documentation &lt;https://docs.pytest.org/en/latest/cache.htmlstepwise&gt;`__ for more info.


- `4188 &lt;https://github.com/pytest-dev/pytest/issues/4188&gt;`_: Make ``--color`` emit colorful dots when not running in verbose mode. Earlier, it would only colorize the test-by-test output if ``--verbose`` was also passed.


- `4225 &lt;https://github.com/pytest-dev/pytest/issues/4225&gt;`_: Improve performance with collection reporting in non-quiet mode with terminals.

  The &quot;collecting …&quot; message is only printed/updated every 0.5s.



Bug Fixes
---------

- `2701 &lt;https://github.com/pytest-dev/pytest/issues/2701&gt;`_: Fix false ``RemovedInPytest4Warning: usage of Session... is deprecated, please use pytest`` warnings.


- `4046 &lt;https://github.com/pytest-dev/pytest/issues/4046&gt;`_: Fix problems with running tests in package ``__init__.py`` files.


- `4260 &lt;https://github.com/pytest-dev/pytest/issues/4260&gt;`_: Swallow warnings during anonymous compilation of source.


- `4262 &lt;https://github.com/pytest-dev/pytest/issues/4262&gt;`_: Fix access denied error when deleting stale directories created by ``tmpdir`` / ``tmp_path``.


- `611 &lt;https://github.com/pytest-dev/pytest/issues/611&gt;`_: Naming a fixture ``request`` will now raise a warning: the ``request`` fixture is internal and
  should not be overwritten as it will lead to internal errors.



Improved Documentation
----------------------

- `4255 &lt;https://github.com/pytest-dev/pytest/issues/4255&gt;`_: Added missing documentation about the fact that module names passed to filter warnings are not regex-escaped.



Trivial/Internal Changes
------------------------

- `4272 &lt;https://github.com/pytest-dev/pytest/issues/4272&gt;`_: Display cachedir also in non-verbose mode if non-default.


- `4277 &lt;https://github.com/pytest-dev/pytest/issues/4277&gt;`_: pdb: improve message about output capturing with ``set_trace``.

  Do not display &quot;IO-capturing turned off/on&quot; when ``-s`` is used to avoid
  confusion.


- `4279 &lt;https://github.com/pytest-dev/pytest/issues/4279&gt;`_: Improve message and stack level of warnings issued by ``monkeypatch.setenv`` when the value of the environment variable is not a ``str``.
   ```
   
  
</details>


 

<details>
  <summary>Links</summary>
  
  - PyPI: https://pypi.org/project/pytest
  - Changelog: https://pyup.io/changelogs/pytest/
  - Homepage: https://docs.pytest.org/en/latest/
</details>

bors bot added a commit to rehandalal/therapist that referenced this pull request Nov 6, 2018

Merge #44
44: Update pytest to 3.10.0 r=rehandalal a=pyup-bot


This PR updates [pytest](https://pypi.org/project/pytest) from **3.9.3** to **3.10.0**.



<details>
  <summary>Changelog</summary>
  
  
   ### 3.10.0
   ```
   ==========================

Features
--------

- `2619 &lt;https://github.com/pytest-dev/pytest/issues/2619&gt;`_: Resume capturing output after ``continue`` with ``__import__(&quot;pdb&quot;).set_trace()``.

  This also adds a new ``pytest_leave_pdb`` hook, and passes in ``pdb`` to the
  existing ``pytest_enter_pdb`` hook.


- `4147 &lt;https://github.com/pytest-dev/pytest/issues/4147&gt;`_: Add ``-sw``, ``--stepwise`` as an alternative to ``--lf -x`` for stopping at the first failure, but starting the next test invocation from that test.  See `the documentation &lt;https://docs.pytest.org/en/latest/cache.htmlstepwise&gt;`__ for more info.


- `4188 &lt;https://github.com/pytest-dev/pytest/issues/4188&gt;`_: Make ``--color`` emit colorful dots when not running in verbose mode. Earlier, it would only colorize the test-by-test output if ``--verbose`` was also passed.


- `4225 &lt;https://github.com/pytest-dev/pytest/issues/4225&gt;`_: Improve performance with collection reporting in non-quiet mode with terminals.

  The &quot;collecting …&quot; message is only printed/updated every 0.5s.



Bug Fixes
---------

- `2701 &lt;https://github.com/pytest-dev/pytest/issues/2701&gt;`_: Fix false ``RemovedInPytest4Warning: usage of Session... is deprecated, please use pytest`` warnings.


- `4046 &lt;https://github.com/pytest-dev/pytest/issues/4046&gt;`_: Fix problems with running tests in package ``__init__.py`` files.


- `4260 &lt;https://github.com/pytest-dev/pytest/issues/4260&gt;`_: Swallow warnings during anonymous compilation of source.


- `4262 &lt;https://github.com/pytest-dev/pytest/issues/4262&gt;`_: Fix access denied error when deleting stale directories created by ``tmpdir`` / ``tmp_path``.


- `611 &lt;https://github.com/pytest-dev/pytest/issues/611&gt;`_: Naming a fixture ``request`` will now raise a warning: the ``request`` fixture is internal and
  should not be overwritten as it will lead to internal errors.



Improved Documentation
----------------------

- `4255 &lt;https://github.com/pytest-dev/pytest/issues/4255&gt;`_: Added missing documentation about the fact that module names passed to filter warnings are not regex-escaped.



Trivial/Internal Changes
------------------------

- `4272 &lt;https://github.com/pytest-dev/pytest/issues/4272&gt;`_: Display cachedir also in non-verbose mode if non-default.


- `4277 &lt;https://github.com/pytest-dev/pytest/issues/4277&gt;`_: pdb: improve message about output capturing with ``set_trace``.

  Do not display &quot;IO-capturing turned off/on&quot; when ``-s`` is used to avoid
  confusion.


- `4279 &lt;https://github.com/pytest-dev/pytest/issues/4279&gt;`_: Improve message and stack level of warnings issued by ``monkeypatch.setenv`` when the value of the environment variable is not a ``str``.
   ```
   
  
</details>


 

<details>
  <summary>Links</summary>
  
  - PyPI: https://pypi.org/project/pytest
  - Changelog: https://pyup.io/changelogs/pytest/
  - Homepage: https://docs.pytest.org/en/latest/
</details>



Co-authored-by: pyup-bot <github-bot@pyup.io>

bors bot added a commit to mozilla/normandy that referenced this pull request Nov 12, 2018

Merge #1617
1617: Scheduled weekly dependency update for week 45 r=peterbe a=pyup-bot






### Update [botocore](https://pypi.org/project/botocore) from **1.12.33** to **1.12.42**.


<details>
  <summary>Changelog</summary>
  
  
   ### 1.12.42
   ```
   =======

* api-change:``mediapackage``: Update mediapackage client to latest version
   ```
   
  
  
   ### 1.12.41
   ```
   =======

* api-change:``medialive``: Update medialive client to latest version
* api-change:``dlm``: Update dlm client to latest version
* api-change:``events``: Update events client to latest version
   ```
   
  
  
   ### 1.12.40
   ```
   =======

* api-change:``dms``: Update dms client to latest version
* api-change:``ce``: Update ce client to latest version
* api-change:``ec2``: Update ec2 client to latest version
   ```
   
  
  
   ### 1.12.39
   ```
   =======

* api-change:``codebuild``: Update codebuild client to latest version
* api-change:``pinpoint``: Update pinpoint client to latest version
* api-change:``ec2``: Update ec2 client to latest version
* api-change:``pinpoint-email``: Update pinpoint-email client to latest version
* api-change:``apigateway``: Update apigateway client to latest version
* api-change:``waf-regional``: Update waf-regional client to latest version
* bugfix:session config: Added the default session configuration tuples back to session.session_vars_map.
   ```
   
  
  
   ### 1.12.38
   ```
   =======

* api-change:``eks``: Update eks client to latest version
* enhancement:Configuration: Added new configuration provider methods allowing for more flexibility in how a botocore session loads a particular configuration value.
* api-change:``serverlessrepo``: Update serverlessrepo client to latest version
   ```
   
  
  
   ### 1.12.37
   ```
   =======

* api-change:``rekognition``: Update rekognition client to latest version
* api-change:``clouddirectory``: Update clouddirectory client to latest version
   ```
   
  
  
   ### 1.12.36
   ```
   =======

* api-change:``servicecatalog``: Update servicecatalog client to latest version
* enhancement:Exceptions: Add the ability to pickle botocore exceptions (`834 &lt;https://github.com/boto/botocore/issues/834&gt;`__)
   ```
   
  
  
   ### 1.12.35
   ```
   =======

* api-change:``mediastore-data``: Update mediastore-data client to latest version
* api-change:``secretsmanager``: Update secretsmanager client to latest version
* api-change:``greengrass``: Update greengrass client to latest version
* api-change:``config``: Update config client to latest version
   ```
   
  
  
   ### 1.12.34
   ```
   =======

* api-change:``chime``: Update chime client to latest version
* api-change:``rds``: Update rds client to latest version
* api-change:``dms``: Update dms client to latest version
   ```
   
  
</details>


 

<details>
  <summary>Links</summary>
  
  - PyPI: https://pypi.org/project/botocore
  - Changelog: https://pyup.io/changelogs/botocore/
  - Repo: https://github.com/boto/botocore
</details>





### Update [future](https://pypi.org/project/future) from **0.17.0** to **0.17.1**.


*The bot wasn't able to find a changelog for this release. [Got an idea?](https://github.com/pyupio/changelogs/issues/new)*

<details>
  <summary>Links</summary>
  
  - PyPI: https://pypi.org/project/future
  - Changelog: https://pyup.io/changelogs/future/
  - Homepage: https://python-future.org
  - Docs: https://pythonhosted.org/future/
</details>





### Update [MarkupSafe](https://pypi.org/project/MarkupSafe) from **1.0** to **1.1.0**.


<details>
  <summary>Changelog</summary>
  
  
   ### 1.1.0
   ```
   -------------

Released 2018-11-05

-   Drop support for Python 2.6 and 3.3.
-   Build wheels for Linux, Mac, and Windows, allowing systems without
    a compiler to take advantage of the C extension speedups. (`104`_)
-   Use newer CPython API on Python 3, resulting in a 1.5x speedup.
    (`64`_)
-   ``escape`` wraps ``__html__`` result in ``Markup``, consistent with
    documented behavior. (`69`_)

.. _64: pallets/markupsafe#64
.. _69: pallets/markupsafe#69
.. _104: pallets/markupsafe#104
   ```
   
  
</details>


 

<details>
  <summary>Links</summary>
  
  - PyPI: https://pypi.org/project/markupsafe
  - Changelog: https://pyup.io/changelogs/markupsafe/
  - Homepage: https://www.palletsprojects.com/p/markupsafe/
</details>





### Update [urllib3](https://pypi.org/project/urllib3) from **1.24** to **1.24.1**.


*The bot wasn't able to find a changelog for this release. [Got an idea?](https://github.com/pyupio/changelogs/issues/new)*

<details>
  <summary>Links</summary>
  
  - PyPI: https://pypi.org/project/urllib3
  - Changelog: https://pyup.io/changelogs/urllib3/
  - Docs: https://urllib3.readthedocs.io/
</details>





### Update [pyparsing](https://pypi.org/project/pyparsing) from **2.2.2** to **2.3.0**.


<details>
  <summary>Changelog</summary>
  
  
   ### 2.3.0
   ```
   -----------------------------
- NEW SUPPORT FOR UNICODE CHARACTER RANGES
  This release introduces the pyparsing_unicode namespace class, defining
  a series of language character sets to simplify the definition of alphas,
  nums, alphanums, and printables in the following language sets:
   . Arabic
   . Chinese
   . Cyrillic
   . Devanagari
   . Greek
   . Hebrew
   . Japanese (including Kanji, Katakana, and Hirigana subsets)
   . Korean
   . Latin1 (includes 7 and 8-bit Latin characters)
   . Thai
   . CJK (combination of Chinese, Japanese, and Korean sets)

  For example, your code can define words using:

    korean_word = Word(pyparsing_unicode.Korean.alphas)

  See their use in the updated examples greetingInGreek.py and
  greetingInKorean.py.

  This namespace class also offers access to these sets using their
  unicode identifiers.

- POSSIBLE API CHANGE: Fixed bug where a parse action that explicitly 
  returned the input ParseResults could add another nesting level in
  the results if the current expression had a results name.

        vals = pp.OneOrMore(pp.pyparsing_common.integer)(&quot;int_values&quot;)
        
        def add_total(tokens):
            tokens[&#39;total&#39;] = sum(tokens)
            return tokens   this line can be removed

        vals.addParseAction(add_total)
        print(vals.parseString(&quot;244 23 13 2343&quot;).dump())

  Before the fix, this code would print (note the extra nesting level):
  
    [244, 23, 13, 2343]
    - int_values: [244, 23, 13, 2343]
      - int_values: [244, 23, 13, 2343]
      - total: 2623
    - total: 2623

  With the fix, this code now prints:
  
    [244, 23, 13, 2343]
    - int_values: [244, 23, 13, 2343]
    - total: 2623

  This fix will change the structure of ParseResults returned if a 
  program defines a parse action that returns the tokens that were 
  sent in. This is not necessary, and statements like &quot;return tokens&quot; 
  in the example above can be safely deleted prior to upgrading to 
  this release, in order to avoid the bug and get the new behavior.

  Reported by seron in Issue 22, nice catch!

- POSSIBLE API CHANGE: Fixed a related bug where a results name 
  erroneously created a second level of hierarchy in the returned 
  ParseResults. The intent for accumulating results names into ParseResults
  is that, in the absence of Group&#39;ing, all names get merged into a
  common namespace. This allows us to write:
  
       key_value_expr = (Word(alphas)(&quot;key&quot;) + &#39;=&#39; + Word(nums)(&quot;value&quot;))
       result = key_value_expr.parseString(&quot;a = 100&quot;) 
    
  and have result structured as {&quot;key&quot;: &quot;a&quot;, &quot;value&quot;: &quot;100&quot;} 
  instead of [{&quot;key&quot;: &quot;a&quot;}, {&quot;value&quot;: &quot;100&quot;}].
  
  However, if a named expression is used in a higher-level non-Group 
  expression that *also* has a name, a false sub-level would be created 
  in the namespace:

        num = pp.Word(pp.nums)
        num_pair = (&quot;[&quot; + (num(&quot;A&quot;) + num(&quot;B&quot;))(&quot;values&quot;) + &quot;]&quot;)
        U = num_pair.parseString(&quot;[ 10 20 ]&quot;)
        print(U.dump())

  Since there is no grouping, &quot;A&quot;, &quot;B&quot;, and &quot;values&quot; should all appear
  at the same level in the results, as:
  
        [&#39;[&#39;, &#39;10&#39;, &#39;20&#39;, &#39;]&#39;]
        - A: &#39;10&#39;
        - B: &#39;20&#39;
        - values: [&#39;10&#39;, &#39;20&#39;]

  Instead, an extra level of &quot;A&quot; and &quot;B&quot; show up under &quot;values&quot;:
  
        [&#39;[&#39;, &#39;10&#39;, &#39;20&#39;, &#39;]&#39;]
        - A: &#39;10&#39;
        - B: &#39;20&#39;
        - values: [&#39;10&#39;, &#39;20&#39;]
          - A: &#39;10&#39;
          - B: &#39;20&#39;

  This bug has been fixed. Now, if this hierarchy is desired, then a
  Group should be added:
  
        num_pair = (&quot;[&quot; + pp.Group(num(&quot;A&quot;) + num(&quot;B&quot;))(&quot;values&quot;) + &quot;]&quot;)

  Giving:
  
        [&#39;[&#39;, [&#39;10&#39;, &#39;20&#39;], &#39;]&#39;]
        - values: [&#39;10&#39;, &#39;20&#39;]
          - A: &#39;10&#39;
          - B: &#39;20&#39;

  But in no case should &quot;A&quot; and &quot;B&quot; appear in multiple levels. This bug-fix
  fixes that.
  
  If you have current code which relies on this behavior, then add or remove
  Groups as necessary to get your intended results structure.
  
  Reported by Athanasios Anastasiou.

- IndexError&#39;s raised in parse actions will get explicitly reraised 
  as ParseExceptions that wrap the original IndexError. Since 
  IndexError sometimes occurs as part of pyparsing&#39;s normal parsing 
  logic, IndexErrors that are raised during a parse action may have
  gotten silently reinterpreted as parsing errors. To retain the 
  information from the IndexError, these exceptions will now be 
  raised as ParseExceptions that reference the original IndexError. 
  This wrapping will only be visible when run under Python3, since it
  emulates &quot;raise ... from ...&quot; syntax. 
  
  Addresses Issue 4, reported by guswns0528.

- Added Char class to simplify defining expressions of a single
  character. (Char(&quot;abc&quot;) is equivalent to Word(&quot;abc&quot;, exact=1))

- Added class PrecededBy to perform lookbehind tests. PrecededBy is 
  used in the same way as FollowedBy, passing in an expression that
  must occur just prior to the current parse location.
  
  For fixed-length expressions like a Literal, Keyword, Char, or a 
  Word with an `exact` or `maxLen` length given, `PrecededBy(expr)` 
  is sufficient. For varying length expressions like a Word with no 
  given maximum length, `PrecededBy` must be constructed with an 
  integer `retreat` argument, as in 
  `PrecededBy(Word(alphas, nums), retreat=10)`, to specify the maximum 
  number of characters pyparsing must look backward to make a match. 
  pyparsing will check all the values from 1 up to retreat characters 
  back from the current parse location.

  When stepping backwards through the input string, PrecededBy does 
  *not* skip over whitespace.
  
  PrecededBy can be created with a results name so that, even though
  it always returns an empty parse result, the result *can* include
  named results.
  
  Idea first suggested in Issue 30 by Freakwill.

- Updated FollowedBy to accept expressions that contain named results,
  so that results names defined in the lookahead expression will be 
  returned, even though FollowedBy always returns an empty list.
  Inspired by the same feature implemented in PrecededBy.
   ```
   
  
</details>


 

<details>
  <summary>Links</summary>
  
  - PyPI: https://pypi.org/project/pyparsing
  - Changelog: https://pyup.io/changelogs/pyparsing/
  - Repo: https://github.com/pyparsing/pyparsing/
  - Docs: https://pythonhosted.org/pyparsing/
</details>





### Update [google-api-core](https://pypi.org/project/google-api-core) from **1.5.0** to **1.5.2**.


*The bot wasn't able to find a changelog for this release. [Got an idea?](https://github.com/pyupio/changelogs/issues/new)*

<details>
  <summary>Links</summary>
  
  - PyPI: https://pypi.org/project/google-api-core
  - Repo: https://github.com/GoogleCloudPlatform/google-cloud-python
</details>





### Update [google-auth](https://pypi.org/project/google-auth) from **1.5.1** to **1.6.0**.


<details>
  <summary>Changelog</summary>
  
  
   ### 1.6.0
   ```
   ------

11-09-2018 11:07 PST

New Features
++++++++++++

- Add google.auth.impersonated_credentials ([299](googleapis/google-auth-library-python#299))

Documentation
+++++++++++++

- Update link to documentation for default credentials ([296](googleapis/google-auth-library-python#296))
- Update github issue templates ([300](googleapis/google-auth-library-python#300))
- Remove punctuation which becomes part of the url ([284](googleapis/google-auth-library-python#284))

Internal / Testing Changes
++++++++++++++++++++++++++

- Update trampoline.sh ([302](googleapis/google-auth-library-python#302))
- Enable static type checking with pytype ([298](googleapis/google-auth-library-python#298))
- Make classifiers in setup.py an array. ([280](googleapis/google-auth-library-python#280))
   ```
   
  
</details>


 

<details>
  <summary>Links</summary>
  
  - PyPI: https://pypi.org/project/google-auth
  - Changelog: https://pyup.io/changelogs/google-auth/
  - Repo: https://github.com/GoogleCloudPlatform/google-auth-library-python
</details>





### Update [googleapis-common-protos](https://pypi.org/project/googleapis-common-protos) from **1.5.3** to **1.5.5**.


*The bot wasn't able to find a changelog for this release. [Got an idea?](https://github.com/pyupio/changelogs/issues/new)*

<details>
  <summary>Links</summary>
  
  - PyPI: https://pypi.org/project/googleapis-common-protos
  - Repo: https://github.com/googleapis/googleapis
</details>





### Update [cachetools](https://pypi.org/project/cachetools) from **2.1.0** to **3.0.0**.


<details>
  <summary>Changelog</summary>
  
  
   ### 3.0.0
   ```
   -------------------

- Officially support Python 3.7.

- Drop Python 3.3 support (breaking change).

- Remove ``missing`` cache constructor parameter (breaking change).

- Remove ``self`` from ``cachedmethod`` key arguments (breaking
  change).

- Add support for ``maxsize=None`` in ``cachetools.func`` decorators.
   ```
   
  
</details>


 

<details>
  <summary>Links</summary>
  
  - PyPI: https://pypi.org/project/cachetools
  - Changelog: https://pyup.io/changelogs/cachetools/
  - Repo: https://github.com/tkem/cachetools
</details>





### Update [boto3](https://pypi.org/project/boto3) from **1.9.33** to **1.9.42**.


<details>
  <summary>Changelog</summary>
  
  
   ### 1.9.42
   ```
   ======

* api-change:``mediapackage``: [``botocore``] Update mediapackage client to latest version
   ```
   
  
  
   ### 1.9.41
   ```
   ======

* api-change:``medialive``: [``botocore``] Update medialive client to latest version
* api-change:``dlm``: [``botocore``] Update dlm client to latest version
* api-change:``events``: [``botocore``] Update events client to latest version
   ```
   
  
  
   ### 1.9.40
   ```
   ======

* api-change:``dms``: [``botocore``] Update dms client to latest version
* api-change:``ce``: [``botocore``] Update ce client to latest version
* api-change:``ec2``: [``botocore``] Update ec2 client to latest version
   ```
   
  
  
   ### 1.9.39
   ```
   ======

* api-change:``codebuild``: [``botocore``] Update codebuild client to latest version
* api-change:``pinpoint``: [``botocore``] Update pinpoint client to latest version
* api-change:``ec2``: [``botocore``] Update ec2 client to latest version
* api-change:``pinpoint-email``: [``botocore``] Update pinpoint-email client to latest version
* api-change:``apigateway``: [``botocore``] Update apigateway client to latest version
* api-change:``waf-regional``: [``botocore``] Update waf-regional client to latest version
* bugfix:session config: [``botocore``] Added the default session configuration tuples back to session.session_vars_map.
   ```
   
  
  
   ### 1.9.38
   ```
   ======

* api-change:``eks``: [``botocore``] Update eks client to latest version
* enhancement:Configuration: [``botocore``] Added new configuration provider methods allowing for more flexibility in how a botocore session loads a particular configuration value.
* api-change:``serverlessrepo``: [``botocore``] Update serverlessrepo client to latest version
   ```
   
  
  
   ### 1.9.37
   ```
   ======

* api-change:``rekognition``: [``botocore``] Update rekognition client to latest version
* api-change:``clouddirectory``: [``botocore``] Update clouddirectory client to latest version
   ```
   
  
  
   ### 1.9.36
   ```
   ======

* api-change:``servicecatalog``: [``botocore``] Update servicecatalog client to latest version
* enhancement:Exceptions: [``botocore``] Add the ability to pickle botocore exceptions (`834 &lt;https://github.com/boto/botocore/issues/834&gt;`__)
   ```
   
  
  
   ### 1.9.35
   ```
   ======

* api-change:``mediastore-data``: [``botocore``] Update mediastore-data client to latest version
* api-change:``secretsmanager``: [``botocore``] Update secretsmanager client to latest version
* api-change:``greengrass``: [``botocore``] Update greengrass client to latest version
* api-change:``config``: [``botocore``] Update config client to latest version
   ```
   
  
  
   ### 1.9.34
   ```
   ======

* api-change:``chime``: [``botocore``] Update chime client to latest version
* api-change:``rds``: [``botocore``] Update rds client to latest version
* api-change:``dms``: [``botocore``] Update dms client to latest version
   ```
   
  
</details>


 

<details>
  <summary>Links</summary>
  
  - PyPI: https://pypi.org/project/boto3
  - Changelog: https://pyup.io/changelogs/boto3/
  - Repo: https://github.com/boto/boto3
</details>





### Update [psycopg2](https://pypi.org/project/psycopg2) from **2.7.5** to **2.7.6.1**.


<details>
  <summary>Changelog</summary>
  
  
   ### 2.7.6
   ```
   ^^^^^^^^^^^^^^^^^^^^^^^^^^^

- Close named cursors if exist, even if `~cursor.execute()` wasn&#39;t called
  (🎫`746`).
- Fixed building on modern FreeBSD versions with Python 3.7 (🎫`755`).
- Fixed hang trying to :sql:`COPY` via `~cursor.execute()` in asynchronous
  connections (🎫`781`).
- Fixed adaptation of arrays of empty arrays (🎫`788`).
- Fixed segfault accessing the connection&#39;s `~connection.readonly` and
  `~connection.deferrable` attributes repeatedly (🎫`790`).
- `~psycopg2.extras.execute_values()` accepts `~psycopg2.sql.Composable`
  objects (🎫`794`).
- `~psycopg2.errorcodes` map updated to PostgreSQL 11.
- Wheel package compiled against PostgreSQL 10.5 libpq and OpenSSL 1.0.2p.
   ```
   
  
</details>


 

<details>
  <summary>Links</summary>
  
  - PyPI: https://pypi.org/project/psycopg2
  - Changelog: https://pyup.io/changelogs/psycopg2/
  - Homepage: http://initd.org/psycopg/
</details>





### Update [pytest](https://pypi.org/project/pytest) from **3.9.3** to **3.10.1**.


<details>
  <summary>Changelog</summary>
  
  
   ### 3.10.1
   ```
   ==========================

Bug Fixes
---------

- `4287 &lt;https://github.com/pytest-dev/pytest/issues/4287&gt;`_: Fix nested usage of debugging plugin (pdb), e.g. with pytester&#39;s ``testdir.runpytest``.


- `4304 &lt;https://github.com/pytest-dev/pytest/issues/4304&gt;`_: Block the ``stepwise`` plugin if ``cacheprovider`` is also blocked, as one depends on the other.


- `4306 &lt;https://github.com/pytest-dev/pytest/issues/4306&gt;`_: Parse ``minversion`` as an actual version and not as dot-separated strings.


- `4310 &lt;https://github.com/pytest-dev/pytest/issues/4310&gt;`_: Fix duplicate collection due to multiple args matching the same packages.


- `4321 &lt;https://github.com/pytest-dev/pytest/issues/4321&gt;`_: Fix ``item.nodeid`` with resolved symlinks.


- `4325 &lt;https://github.com/pytest-dev/pytest/issues/4325&gt;`_: Fix collection of direct symlinked files, where the target does not match ``python_files``.


- `4329 &lt;https://github.com/pytest-dev/pytest/issues/4329&gt;`_: Fix TypeError in report_collect with _collect_report_last_write.



Trivial/Internal Changes
------------------------

- `4305 &lt;https://github.com/pytest-dev/pytest/issues/4305&gt;`_: Replace byte/unicode helpers in test_capture with python level syntax.
   ```
   
  
  
   ### 3.10.0
   ```
   ==========================

Features
--------

- `2619 &lt;https://github.com/pytest-dev/pytest/issues/2619&gt;`_: Resume capturing output after ``continue`` with ``__import__(&quot;pdb&quot;).set_trace()``.

  This also adds a new ``pytest_leave_pdb`` hook, and passes in ``pdb`` to the
  existing ``pytest_enter_pdb`` hook.


- `4147 &lt;https://github.com/pytest-dev/pytest/issues/4147&gt;`_: Add ``--sw``, ``--stepwise`` as an alternative to ``--lf -x`` for stopping at the first failure, but starting the next test invocation from that test.  See `the documentation &lt;https://docs.pytest.org/en/latest/cache.htmlstepwise&gt;`__ for more info.


- `4188 &lt;https://github.com/pytest-dev/pytest/issues/4188&gt;`_: Make ``--color`` emit colorful dots when not running in verbose mode. Earlier, it would only colorize the test-by-test output if ``--verbose`` was also passed.


- `4225 &lt;https://github.com/pytest-dev/pytest/issues/4225&gt;`_: Improve performance with collection reporting in non-quiet mode with terminals.

  The &quot;collecting …&quot; message is only printed/updated every 0.5s.



Bug Fixes
---------

- `2701 &lt;https://github.com/pytest-dev/pytest/issues/2701&gt;`_: Fix false ``RemovedInPytest4Warning: usage of Session... is deprecated, please use pytest`` warnings.


- `4046 &lt;https://github.com/pytest-dev/pytest/issues/4046&gt;`_: Fix problems with running tests in package ``__init__.py`` files.


- `4260 &lt;https://github.com/pytest-dev/pytest/issues/4260&gt;`_: Swallow warnings during anonymous compilation of source.


- `4262 &lt;https://github.com/pytest-dev/pytest/issues/4262&gt;`_: Fix access denied error when deleting stale directories created by ``tmpdir`` / ``tmp_path``.


- `611 &lt;https://github.com/pytest-dev/pytest/issues/611&gt;`_: Naming a fixture ``request`` will now raise a warning: the ``request`` fixture is internal and
  should not be overwritten as it will lead to internal errors.

- `4266 &lt;https://github.com/pytest-dev/pytest/issues/4266&gt;`_: Handle (ignore) exceptions raised during collection, e.g. with Django&#39;s LazySettings proxy class.



Improved Documentation
----------------------

- `4255 &lt;https://github.com/pytest-dev/pytest/issues/4255&gt;`_: Added missing documentation about the fact that module names passed to filter warnings are not regex-escaped.



Trivial/Internal Changes
------------------------

- `4272 &lt;https://github.com/pytest-dev/pytest/issues/4272&gt;`_: Display cachedir also in non-verbose mode if non-default.


- `4277 &lt;https://github.com/pytest-dev/pytest/issues/4277&gt;`_: pdb: improve message about output capturing with ``set_trace``.

  Do not display &quot;IO-capturing turned off/on&quot; when ``-s`` is used to avoid
  confusion.


- `4279 &lt;https://github.com/pytest-dev/pytest/issues/4279&gt;`_: Improve message and stack level of warnings issued by ``monkeypatch.setenv`` when the value of the environment variable is not a ``str``.
   ```
   
  
</details>


 

<details>
  <summary>Links</summary>
  
  - PyPI: https://pypi.org/project/pytest
  - Changelog: https://pyup.io/changelogs/pytest/
  - Homepage: https://docs.pytest.org/en/latest/
</details>





### Update [pytest-testrail](https://pypi.org/project/pytest-testrail) from **2.3.0** to **2.3.1**.


<details>
  <summary>Changelog</summary>
  
  
  
</details>


 

<details>
  <summary>Links</summary>
  
  - PyPI: https://pypi.org/project/pytest-testrail
  - Changelog: https://pyup.io/changelogs/pytest-testrail/
  - Repo: http://github.com/allankp/pytest-testrail/
</details>





### Update [requests](https://pypi.org/project/requests) from **2.20.0** to **2.20.1**.


<details>
  <summary>Changelog</summary>
  
  
   ### 2.20.1
   ```
   -------------------

**Bugfixes**

- Fixed bug with unintended Authorization header stripping for
  redirects using default ports (http/80, https/443).
   ```
   
  
</details>


 

<details>
  <summary>Links</summary>
  
  - PyPI: https://pypi.org/project/requests
  - Changelog: https://pyup.io/changelogs/requests/
  - Homepage: http://python-requests.org
</details>





### Update [Sphinx](https://pypi.org/project/Sphinx) from **1.8.1** to **1.8.2**.


<details>
  <summary>Changelog</summary>
  
  
   ### 1.8.2
   ```
   =====================================

Incompatible changes
--------------------

* 5497: Do not include MathJax.js and jsmath.js unless it is really needed

Features added
--------------

* 5471: Show appropriate deprecation warnings

Bugs fixed
----------

* 5490: latex: enumerated list causes a crash with recommonmark
* 5492: sphinx-build fails to build docs w/ Python &lt; 3.5.2
* 3704: latex: wrong ``\label`` positioning for figures with a legend
* 5496: C++, fix assertion when a symbol is declared more than twice.
* 5493: gettext: crashed with broken template
* 5495: csv-table directive with file option in included file is broken (refs:
  4821)
* 5498: autodoc: unable to find type hints for a ``functools.partial``
* 5480: autodoc: unable to find type hints for unresolvable Forward references
* 5419: incompatible math_block node has been generated
* 5548: Fix ensuredir() in case of pre-existing file
* 5549: graphviz Correctly deal with non-existing static dir
* 3002: i18n: multiple footnote_references referring same footnote causes
  duplicated node_ids
* 5563: latex: footnote_references generated by extension causes LaTeX builder
  crashed
* 5561: make all-pdf fails with old xindy version
* 5557: quickstart: --no-batchfile isn&#39;t honored
* 3080: texinfo: multiline rubrics are broken
* 3080: texinfo: multiline citations are broken
   ```
   
  
</details>


 

<details>
  <summary>Links</summary>
  
  - PyPI: https://pypi.org/project/sphinx
  - Changelog: https://pyup.io/changelogs/sphinx/
  - Homepage: http://sphinx-doc.org/
</details>







Co-authored-by: pyup-bot <github-bot@pyup.io>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment