{"action":"closed","number":138,"pull_request":{"url":"https://api.github.com/repos/pyros-dev/rostful/pulls/138","id":212798571,"node_id":"MDExOlB1bGxSZXF1ZXN0MjEyNzk4NTcx","html_url":"https://github.com/pyros-dev/rostful/pull/138","diff_url":"https://github.com/pyros-dev/rostful/pull/138.diff","patch_url":"https://github.com/pyros-dev/rostful/pull/138.patch","issue_url":"https://api.github.com/repos/pyros-dev/rostful/issues/138","number":138,"state":"closed","locked":false,"title":"Scheduled weekly dependency update for week 35","user":{"login":"pyup-bot","id":16239342,"node_id":"MDQ6VXNlcjE2MjM5MzQy","avatar_url":"https://avatars0.githubusercontent.com/u/16239342?v=4","gravatar_id":"","url":"https://api.github.com/users/pyup-bot","html_url":"https://github.com/pyup-bot","followers_url":"https://api.github.com/users/pyup-bot/followers","following_url":"https://api.github.com/users/pyup-bot/following{/other_user}","gists_url":"https://api.github.com/users/pyup-bot/gists{/gist_id}","starred_url":"https://api.github.com/users/pyup-bot/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/pyup-bot/subscriptions","organizations_url":"https://api.github.com/users/pyup-bot/orgs","repos_url":"https://api.github.com/users/pyup-bot/repos","events_url":"https://api.github.com/users/pyup-bot/events{/privacy}","received_events_url":"https://api.github.com/users/pyup-bot/received_events","type":"User","site_admin":false},"body":"\n\n\n\n\n### Update [pytest](https://pypi.org/project/pytest) from **3.5.0** to **3.7.4**.\n\n\n<details>\n  <summary>Changelog</summary>\n  \n  \n   ### 3.7.4\n   ```\n   =========================\n\nBug Fixes\n---------\n\n- `3506 &lt;https://github.com/pytest-dev/pytest/issues/3506&gt;`_: Fix possible infinite recursion when writing ``.pyc`` files.\n\n\n- `3853 &lt;https://github.com/pytest-dev/pytest/issues/3853&gt;`_: Cache plugin now obeys the ``-q`` flag when ``--last-failed`` and ``--failed-first`` flags are used.\n\n\n- `3883 &lt;https://github.com/pytest-dev/pytest/issues/3883&gt;`_: Fix bad console output when using ``console_output_style=classic``.\n\n\n- `3888 &lt;https://github.com/pytest-dev/pytest/issues/3888&gt;`_: Fix macOS specific code using ``capturemanager`` plugin in doctests.\n\n\n\nImproved Documentation\n----------------------\n\n- `3902 &lt;https://github.com/pytest-dev/pytest/issues/3902&gt;`_: Fix pytest.org links\n   ```\n   \n  \n  \n   ### 3.7.3\n   ```\n   =========================\n\nBug Fixes\n---------\n\n- `3033 &lt;https://github.com/pytest-dev/pytest/issues/3033&gt;`_: Fixtures during teardown can again use ``capsys`` and ``capfd`` to inspect output captured during tests.\n\n\n- `3773 &lt;https://github.com/pytest-dev/pytest/issues/3773&gt;`_: Fix collection of tests from ``__init__.py`` files if they match the ``python_files`` configuration option.\n\n\n- `3796 &lt;https://github.com/pytest-dev/pytest/issues/3796&gt;`_: Fix issue where teardown of fixtures of consecutive sub-packages were executed once, at the end of the outer\n  package.\n\n\n- `3816 &lt;https://github.com/pytest-dev/pytest/issues/3816&gt;`_: Fix bug where ``--show-capture=no`` option would still show logs printed during fixture teardown.\n\n\n- `3819 &lt;https://github.com/pytest-dev/pytest/issues/3819&gt;`_: Fix ``stdout/stderr`` not getting captured when real-time cli logging is active.\n\n\n- `3843 &lt;https://github.com/pytest-dev/pytest/issues/3843&gt;`_: Fix collection error when specifying test functions directly in the command line using ``test.py::test`` syntax together with ``--doctest-modules``.\n\n\n- `3848 &lt;https://github.com/pytest-dev/pytest/issues/3848&gt;`_: Fix bugs where unicode arguments could not be passed to ``testdir.runpytest`` on Python 2.\n\n\n- `3854 &lt;https://github.com/pytest-dev/pytest/issues/3854&gt;`_: Fix double collection of tests within packages when the filename starts with a capital letter.\n\n\n\nImproved Documentation\n----------------------\n\n- `3824 &lt;https://github.com/pytest-dev/pytest/issues/3824&gt;`_: Added example for multiple glob pattern matches in ``python_files``.\n\n\n- `3833 &lt;https://github.com/pytest-dev/pytest/issues/3833&gt;`_: Added missing docs for ``pytester.Testdir``.\n\n\n- `3870 &lt;https://github.com/pytest-dev/pytest/issues/3870&gt;`_: Correct documentation for setuptools integration.\n\n\n\nTrivial/Internal Changes\n------------------------\n\n- `3826 &lt;https://github.com/pytest-dev/pytest/issues/3826&gt;`_: Replace broken type annotations with type comments.\n\n\n- `3845 &lt;https://github.com/pytest-dev/pytest/issues/3845&gt;`_: Remove a reference to issue `568 &lt;https://github.com/pytest-dev/pytest/issues/568&gt;`_ from the documentation, which has since been\n  fixed.\n   ```\n   \n  \n  \n   ### 3.7.2\n   ```\n   =========================\n\nBug Fixes\n---------\n\n- `3671 &lt;https://github.com/pytest-dev/pytest/issues/3671&gt;`_: Fix ``filterwarnings`` not being registered as a builtin mark.\n\n\n- `3768 &lt;https://github.com/pytest-dev/pytest/issues/3768&gt;`_, `3789 &lt;https://github.com/pytest-dev/pytest/issues/3789&gt;`_: Fix test collection from packages mixed with normal directories.\n\n\n- `3771 &lt;https://github.com/pytest-dev/pytest/issues/3771&gt;`_: Fix infinite recursion during collection if a ``pytest_ignore_collect`` hook returns ``False`` instead of ``None``.\n\n\n- `3774 &lt;https://github.com/pytest-dev/pytest/issues/3774&gt;`_: Fix bug where decorated fixtures would lose functionality (for example ``mock.patch``).\n\n\n- `3775 &lt;https://github.com/pytest-dev/pytest/issues/3775&gt;`_: Fix bug where importing modules or other objects with prefix ``pytest_`` prefix would raise a ``PluginValidationError``.\n\n\n- `3788 &lt;https://github.com/pytest-dev/pytest/issues/3788&gt;`_: Fix ``AttributeError`` during teardown of ``TestCase`` subclasses which raise an exception during ``__init__``.\n\n\n- `3804 &lt;https://github.com/pytest-dev/pytest/issues/3804&gt;`_: Fix traceback reporting for exceptions with ``__cause__`` cycles.\n\n\n\nImproved Documentation\n----------------------\n\n- `3746 &lt;https://github.com/pytest-dev/pytest/issues/3746&gt;`_: Add documentation for ``metafunc.config`` that had been mistakenly hidden.\n   ```\n   \n  \n  \n   ### 3.7.1\n   ```\n   =========================\n\nBug Fixes\n---------\n\n- `3473 &lt;https://github.com/pytest-dev/pytest/issues/3473&gt;`_: Raise immediately if ``approx()`` is given an expected value of a type it doesn&#39;t understand (e.g. strings, nested dicts, etc.).\n\n\n- `3712 &lt;https://github.com/pytest-dev/pytest/issues/3712&gt;`_: Correctly represent the dimensions of an numpy array when calling ``repr()`` on ``approx()``.\n\n- `3742 &lt;https://github.com/pytest-dev/pytest/issues/3742&gt;`_: Fix incompatibility with third party plugins during collection, which produced the error ``object has no attribute &#39;_collectfile&#39;``.\n\n- `3745 &lt;https://github.com/pytest-dev/pytest/issues/3745&gt;`_: Display the absolute path if ``cache_dir`` is not relative to the ``rootdir`` instead of failing.\n\n\n- `3747 &lt;https://github.com/pytest-dev/pytest/issues/3747&gt;`_: Fix compatibility problem with plugins and the warning code issued by fixture functions when they are called directly.\n\n\n- `3748 &lt;https://github.com/pytest-dev/pytest/issues/3748&gt;`_: Fix infinite recursion in ``pytest.approx`` with arrays in ``numpy&lt;1.13``.\n\n\n- `3757 &lt;https://github.com/pytest-dev/pytest/issues/3757&gt;`_: Pin pathlib2 to ``&gt;=2.2.0`` as we require ``__fspath__`` support.\n\n\n- `3763 &lt;https://github.com/pytest-dev/pytest/issues/3763&gt;`_: Fix ``TypeError`` when the assertion message is ``bytes`` in python 3.\n   ```\n   \n  \n  \n   ### 3.7.0\n   ```\n   =========================\n\nDeprecations and Removals\n-------------------------\n\n- `2639 &lt;https://github.com/pytest-dev/pytest/issues/2639&gt;`_: ``pytest_namespace`` has been deprecated.\n\n  See the documentation for ``pytest_namespace`` hook for suggestions on how to deal\n  with this in plugins which use this functionality.\n\n\n- `3661 &lt;https://github.com/pytest-dev/pytest/issues/3661&gt;`_: Calling a fixture function directly, as opposed to request them in a test function, now issues a ``RemovedInPytest4Warning``. It will be changed into an error in pytest ``4.0``.\n\n  This is a great source of confusion to new users, which will often call the fixture functions and request them from test functions interchangeably, which breaks the fixture resolution model.\n\n\n\nFeatures\n--------\n\n- `2283 &lt;https://github.com/pytest-dev/pytest/issues/2283&gt;`_: New ``package`` fixture scope: fixtures are finalized when the last test of a *package* finishes. This feature is considered **experimental**, so use it sparingly.\n\n\n- `3576 &lt;https://github.com/pytest-dev/pytest/issues/3576&gt;`_: ``Node.add_marker`` now supports an ``append=True/False`` parameter to determine whether the mark comes last (default) or first.\n\n\n- `3579 &lt;https://github.com/pytest-dev/pytest/issues/3579&gt;`_: Fixture ``caplog`` now has a ``messages`` property, providing convenient access to the format-interpolated log messages without the extra data provided by the formatter/handler.\n\n\n- `3610 &lt;https://github.com/pytest-dev/pytest/issues/3610&gt;`_: New ``--trace`` option to enter the debugger at the start of a test.\n\n\n- `3623 &lt;https://github.com/pytest-dev/pytest/issues/3623&gt;`_: Introduce ``pytester.copy_example`` as helper to do acceptance tests against examples from the project.\n\n\n\nBug Fixes\n---------\n\n- `2220 &lt;https://github.com/pytest-dev/pytest/issues/2220&gt;`_: Fix a bug where fixtures overridden by direct parameters (for example parametrization) were being instantiated even if they were not being used by a test.\n\n\n- `3695 &lt;https://github.com/pytest-dev/pytest/issues/3695&gt;`_: Fix ``ApproxNumpy`` initialisation argument mixup, ``abs`` and ``rel`` tolerances were flipped causing strange comparsion results.\n  Add tests to check ``abs`` and ``rel`` tolerances for ``np.array`` and test for expecting ``nan`` with ``np.array()``\n\n\n- `980 &lt;https://github.com/pytest-dev/pytest/issues/980&gt;`_: Fix truncated locals output in verbose mode.\n\n\n\nImproved Documentation\n----------------------\n\n- `3295 &lt;https://github.com/pytest-dev/pytest/issues/3295&gt;`_: Correct the usage documentation of ``--last-failed-no-failures`` by adding the missing ``--last-failed`` argument in the presented examples, because they are misleading and lead to think that the missing argument is not needed.\n\n\n\nTrivial/Internal Changes\n------------------------\n\n- `3519 &lt;https://github.com/pytest-dev/pytest/issues/3519&gt;`_: Now a ``README.md`` file is created in ``.pytest_cache`` to make it clear why the directory exists.\n   ```\n   \n  \n  \n   ### 3.6.4\n   ```\n   =========================\n\nBug Fixes\n---------\n\n- Invoke pytest using ``-mpytest`` so ``sys.path`` does not get polluted by packages installed in ``site-packages``. (`742 &lt;https://github.com/pytest-dev/pytest/issues/742&gt;`_)\n\n\nImproved Documentation\n----------------------\n\n- Use ``smtp_connection`` instead of ``smtp`` in fixtures documentation to avoid possible confusion. (`3592 &lt;https://github.com/pytest-dev/pytest/issues/3592&gt;`_)\n\n\nTrivial/Internal Changes\n------------------------\n\n- Remove obsolete ``__future__`` imports. (`2319 &lt;https://github.com/pytest-dev/pytest/issues/2319&gt;`_)\n\n- Add CITATION to provide information on how to formally cite pytest. (`3402 &lt;https://github.com/pytest-dev/pytest/issues/3402&gt;`_)\n\n- Replace broken type annotations with type comments. (`3635 &lt;https://github.com/pytest-dev/pytest/issues/3635&gt;`_)\n\n- Pin ``pluggy`` to ``&lt;0.8``. (`3727 &lt;https://github.com/pytest-dev/pytest/issues/3727&gt;`_)\n   ```\n   \n  \n  \n   ### 3.6.3\n   ```\n   =========================\n\nBug Fixes\n---------\n\n- Fix ``ImportWarning`` triggered by explicit relative imports in\n  assertion-rewritten package modules. (`3061\n  &lt;https://github.com/pytest-dev/pytest/issues/3061&gt;`_)\n\n- Fix error in ``pytest.approx`` when dealing with 0-dimension numpy\n  arrays. (`3593 &lt;https://github.com/pytest-dev/pytest/issues/3593&gt;`_)\n\n- No longer raise ``ValueError`` when using the ``get_marker`` API. (`3605\n  &lt;https://github.com/pytest-dev/pytest/issues/3605&gt;`_)\n\n- Fix problem where log messages with non-ascii characters would not\n  appear in the output log file.\n  (`3630 &lt;https://github.com/pytest-dev/pytest/issues/3630&gt;`_)\n\n- No longer raise ``AttributeError`` when legacy marks can&#39;t be stored in\n  functions. (`3631 &lt;https://github.com/pytest-dev/pytest/issues/3631&gt;`_)\n\n\nImproved Documentation\n----------------------\n\n- The description above the example for ``pytest.mark.skipif`` now better\n  matches the code. (`3611\n  &lt;https://github.com/pytest-dev/pytest/issues/3611&gt;`_)\n\n\nTrivial/Internal Changes\n------------------------\n\n- Internal refactoring: removed unused ``CallSpec2tox ._globalid_args``\n  attribute and ``metafunc`` parameter from ``CallSpec2.copy()``. (`3598\n  &lt;https://github.com/pytest-dev/pytest/issues/3598&gt;`_)\n\n- Silence usage of ``reduce`` warning in Python 2 (`3609\n  &lt;https://github.com/pytest-dev/pytest/issues/3609&gt;`_)\n\n- Fix usage of ``attr.ib`` deprecated ``convert`` parameter. (`3653\n  &lt;https://github.com/pytest-dev/pytest/issues/3653&gt;`_)\n   ```\n   \n  \n  \n   ### 3.6.2\n   ```\n   =========================\n\nBug Fixes\n---------\n\n- Fix regression in ``Node.add_marker`` by extracting the mark object of a\n  ``MarkDecorator``. (`3555\n  &lt;https://github.com/pytest-dev/pytest/issues/3555&gt;`_)\n\n- Warnings without ``location`` were reported as ``None``. This is corrected to\n  now report ``&lt;undetermined location&gt;``. (`3563\n  &lt;https://github.com/pytest-dev/pytest/issues/3563&gt;`_)\n\n- Continue to call finalizers in the stack when a finalizer in a former scope\n  raises an exception. (`3569\n  &lt;https://github.com/pytest-dev/pytest/issues/3569&gt;`_)\n\n- Fix encoding error with ``print`` statements in doctests (`3583\n  &lt;https://github.com/pytest-dev/pytest/issues/3583&gt;`_)\n\n\nImproved Documentation\n----------------------\n\n- Add documentation for the ``--strict`` flag. (`3549\n  &lt;https://github.com/pytest-dev/pytest/issues/3549&gt;`_)\n\n\nTrivial/Internal Changes\n------------------------\n\n- Update old quotation style to parens in fixture.rst documentation. (`3525\n  &lt;https://github.com/pytest-dev/pytest/issues/3525&gt;`_)\n\n- Improve display of hint about ``--fulltrace`` with ``KeyboardInterrupt``.\n  (`3545 &lt;https://github.com/pytest-dev/pytest/issues/3545&gt;`_)\n\n- pytest&#39;s testsuite is no longer runnable through ``python setup.py test`` --\n  instead invoke ``pytest`` or ``tox`` directly. (`3552\n  &lt;https://github.com/pytest-dev/pytest/issues/3552&gt;`_)\n\n- Fix typo in documentation (`3567\n  &lt;https://github.com/pytest-dev/pytest/issues/3567&gt;`_)\n   ```\n   \n  \n  \n   ### 3.6.1\n   ```\n   =========================\n\nBug Fixes\n---------\n\n- Fixed a bug where stdout and stderr were logged twice by junitxml when a test\n  was marked xfail. (`3491\n  &lt;https://github.com/pytest-dev/pytest/issues/3491&gt;`_)\n\n- Fix ``usefixtures`` mark applyed to unittest tests by correctly instantiating\n  ``FixtureInfo``. (`3498\n  &lt;https://github.com/pytest-dev/pytest/issues/3498&gt;`_)\n\n- Fix assertion rewriter compatibility with libraries that monkey patch\n  ``file`` objects. (`3503\n  &lt;https://github.com/pytest-dev/pytest/issues/3503&gt;`_)\n\n\nImproved Documentation\n----------------------\n\n- Added a section on how to use fixtures as factories to the fixture\n  documentation. (`3461 &lt;https://github.com/pytest-dev/pytest/issues/3461&gt;`_)\n\n\nTrivial/Internal Changes\n------------------------\n\n- Enable caching for pip/pre-commit in order to reduce build time on\n  travis/appveyor. (`3502\n  &lt;https://github.com/pytest-dev/pytest/issues/3502&gt;`_)\n\n- Switch pytest to the src/ layout as we already suggested it for good practice\n  - now we implement it as well. (`3513\n  &lt;https://github.com/pytest-dev/pytest/issues/3513&gt;`_)\n\n- Fix if in tests to support 3.7.0b5, where a docstring handling in AST got\n  reverted. (`3530 &lt;https://github.com/pytest-dev/pytest/issues/3530&gt;`_)\n\n- Remove some python2.5 compatibility code. (`3529\n  &lt;https://github.com/pytest-dev/pytest/issues/3529&gt;`_)\n   ```\n   \n  \n  \n   ### 3.6.0\n   ```\n   =========================\n\nFeatures\n--------\n\n- Revamp the internals of the ``pytest.mark`` implementation with correct per\n  node handling which fixes a number of long standing bugs caused by the old\n  design. This introduces new ``Node.iter_markers(name)`` and\n  ``Node.get_closest_mark(name)`` APIs. Users are **strongly encouraged** to\n  read the `reasons for the revamp in the docs\n  &lt;https://docs.pytest.org/en/latest/mark.htmlmarker-revamp-and-iteration&gt;`_,\n  or jump over to details about `updating existing code to use the new APIs\n  &lt;https://docs.pytest.org/en/latest/mark.htmlupdating-code&gt;`_. (`3317\n  &lt;https://github.com/pytest-dev/pytest/issues/3317&gt;`_)\n\n- Now when ``pytest.fixture`` is applied more than once to the same function a\n  ``ValueError`` is raised. This buggy behavior would cause surprising problems\n  and if was working for a test suite it was mostly by accident. (`2334\n  &lt;https://github.com/pytest-dev/pytest/issues/2334&gt;`_)\n\n- Support for Python 3.7&#39;s builtin ``breakpoint()`` method, see `Using the\n  builtin breakpoint function\n  &lt;https://docs.pytest.org/en/latest/usage.htmlbreakpoint-builtin&gt;`_ for\n  details. (`3180 &lt;https://github.com/pytest-dev/pytest/issues/3180&gt;`_)\n\n- ``monkeypatch`` now supports a ``context()`` function which acts as a context\n  manager which undoes all patching done within the ``with`` block. (`3290\n  &lt;https://github.com/pytest-dev/pytest/issues/3290&gt;`_)\n\n- The ``--pdb`` option now causes KeyboardInterrupt to enter the debugger,\n  instead of stopping the test session. On python 2.7, hitting CTRL+C again\n  exits the debugger. On python 3.2 and higher, use CTRL+D. (`3299\n  &lt;https://github.com/pytest-dev/pytest/issues/3299&gt;`_)\n\n- pytest not longer changes the log level of the root logger when the\n  ``log-level`` parameter has greater numeric value than that of the level of\n  the root logger, which makes it play better with custom logging configuration\n  in user code. (`3307 &lt;https://github.com/pytest-dev/pytest/issues/3307&gt;`_)\n\n\nBug Fixes\n---------\n\n- A rare race-condition which might result in corrupted ``.pyc`` files on\n  Windows has been hopefully solved. (`3008\n  &lt;https://github.com/pytest-dev/pytest/issues/3008&gt;`_)\n\n- Also use iter_marker for discovering the marks applying for marker\n  expressions from the cli to avoid the bad data from the legacy mark storage.\n  (`3441 &lt;https://github.com/pytest-dev/pytest/issues/3441&gt;`_)\n\n- When showing diffs of failed assertions where the contents contain only\n  whitespace, escape them using ``repr()`` first to make it easy to spot the\n  differences. (`3443 &lt;https://github.com/pytest-dev/pytest/issues/3443&gt;`_)\n\n\nImproved Documentation\n----------------------\n\n- Change documentation copyright year to a range which auto-updates itself each\n  time it is published. (`3303\n  &lt;https://github.com/pytest-dev/pytest/issues/3303&gt;`_)\n\n\nTrivial/Internal Changes\n------------------------\n\n- ``pytest`` now depends on the `python-atomicwrites\n  &lt;https://github.com/untitaker/python-atomicwrites&gt;`_ library. (`3008\n  &lt;https://github.com/pytest-dev/pytest/issues/3008&gt;`_)\n\n- Update all pypi.python.org URLs to pypi.org. (`3431\n  &lt;https://github.com/pytest-dev/pytest/issues/3431&gt;`_)\n\n- Detect `pytest_` prefixed hooks using the internal plugin manager since\n  ``pluggy`` is deprecating the ``implprefix`` argument to ``PluginManager``.\n  (`3487 &lt;https://github.com/pytest-dev/pytest/issues/3487&gt;`_)\n\n- Import ``Mapping`` and ``Sequence`` from ``_pytest.compat`` instead of\n  directly from ``collections`` in ``python_api.py::approx``. Add ``Mapping``\n  to ``_pytest.compat``, import it from ``collections`` on python 2, but from\n  ``collections.abc`` on Python 3 to avoid a ``DeprecationWarning`` on Python\n  3.7 or newer. (`3497 &lt;https://github.com/pytest-dev/pytest/issues/3497&gt;`_)\n   ```\n   \n  \n  \n   ### 3.5.1\n   ```\n   =========================\n\n\nBug Fixes\n---------\n\n- Reset ``sys.last_type``, ``sys.last_value`` and ``sys.last_traceback`` before\n  each test executes. Those attributes are added by pytest during the test run\n  to aid debugging, but were never reset so they would create a leaking\n  reference to the last failing test&#39;s frame which in turn could never be\n  reclaimed by the garbage collector. (`2798\n  &lt;https://github.com/pytest-dev/pytest/issues/2798&gt;`_)\n\n- ``pytest.raises`` now raises ``TypeError`` when receiving an unknown keyword\n  argument. (`3348 &lt;https://github.com/pytest-dev/pytest/issues/3348&gt;`_)\n\n- ``pytest.raises`` now works with exception classes that look like iterables.\n  (`3372 &lt;https://github.com/pytest-dev/pytest/issues/3372&gt;`_)\n\n\nImproved Documentation\n----------------------\n\n- Fix typo in ``caplog`` fixture documentation, which incorrectly identified\n  certain attributes as methods. (`3406\n  &lt;https://github.com/pytest-dev/pytest/issues/3406&gt;`_)\n\n\nTrivial/Internal Changes\n------------------------\n\n- Added a more indicative error message when parametrizing a function whose\n  argument takes a default value. (`3221\n  &lt;https://github.com/pytest-dev/pytest/issues/3221&gt;`_)\n\n- Remove internal ``_pytest.terminal.flatten`` function in favor of\n  ``more_itertools.collapse``. (`3330\n  &lt;https://github.com/pytest-dev/pytest/issues/3330&gt;`_)\n\n- Import some modules from ``collections.abc`` instead of ``collections`` as\n  the former modules trigger ``DeprecationWarning`` in Python 3.7. (`3339\n  &lt;https://github.com/pytest-dev/pytest/issues/3339&gt;`_)\n\n- record_property is no longer experimental, removing the warnings was\n  forgotten. (`3360 &lt;https://github.com/pytest-dev/pytest/issues/3360&gt;`_)\n\n- Mention in documentation and CLI help that fixtures with leading ``_`` are\n  printed by ``pytest --fixtures`` only if the ``-v`` option is added. (`3398\n  &lt;https://github.com/pytest-dev/pytest/issues/3398&gt;`_)\n   ```\n   \n  \n</details>\n\n\n \n\n<details>\n  <summary>Links</summary>\n  \n  - PyPI: https://pypi.org/project/pytest\n  - Changelog: https://pyup.io/changelogs/pytest/\n  - Homepage: https://docs.pytest.org/en/latest/\n</details>\n\n\n\n\n\n### Update [pytest-xdist](https://pypi.org/project/pytest-xdist) from **1.22.2** to **1.23.0**.\n\n\n<details>\n  <summary>Changelog</summary>\n  \n  \n   ### 1.23.0\n   ```\n   ================================\n\nFeatures\n--------\n\n- `330 &lt;https://github.com/pytest-dev/pytest-xdist/issues/330&gt;`_: Improve collection performance by reducing the number of events sent to ``master`` node.\n   ```\n   \n  \n  \n   ### 1.22.5\n   ```\n   ================================\n\nBug Fixes\n---------\n\n- `321 &lt;https://github.com/pytest-dev/pytest-xdist/issues/321&gt;`_: Revert change that dropped support for ``pytest&lt;3.4`` and require ``six``.\n\n  This change caused problems in some installations, and was a mistaken\n  in the first place as we should not change version requirements\n  in bug-fix releases unless they fix an actual bug.\n   ```\n   \n  \n  \n   ### 1.22.4\n   ```\n   ================================\n\nBug Fixes\n---------\n\n- `305 &lt;https://github.com/pytest-dev/pytest-xdist/issues/305&gt;`_: Remove last references to obsolete ``py.code``.\n\n  Remove some unnecessary references to ``py.builtin``.\n\n- `316 &lt;https://github.com/pytest-dev/pytest-xdist/issues/316&gt;`_: Workaround cpu detection on Travis CI.\n   ```\n   \n  \n  \n   ### 1.22.3\n   ```\n   ================================\n\nBug Fixes\n---------\n\n- Fix issue of virtualized or containerized environments not reporting the number of CPUs correctly. (`9 &lt;https://github.com/pytest-dev/pytest-xdist/issues/9&gt;`_)\n\n\nTrivial Changes\n---------------\n\n- Make all classes subclass from ``object`` and fix ``super()`` call in ``LoadFileScheduling``; (`297 &lt;https://github.com/pytest-dev/pytest-xdist/issues/297&gt;`_)\n   ```\n   \n  \n</details>\n\n\n \n\n<details>\n  <summary>Links</summary>\n  \n  - PyPI: https://pypi.org/project/pytest-xdist\n  - Changelog: https://pyup.io/changelogs/pytest-xdist/\n  - Repo: https://github.com/pytest-dev/pytest-xdist\n</details>\n\n\n\n\n\n### Update [hypothesis](https://pypi.org/project/hypothesis) from **3.56.3** to **3.70.3**.\n\n\n*The bot wasn't able to find a changelog for this release. [Got an idea?](https://github.com/pyupio/changelogs/issues/new)*\n\n<details>\n  <summary>Links</summary>\n  \n  - PyPI: https://pypi.org/project/hypothesis\n  - Repo: https://github.com/HypothesisWorks/hypothesis/tree/master/hypothesis-python\n</details>\n\n\n\n\n\n### Update [numpy](https://pypi.org/project/numpy) from **1.14.2** to **1.15.1**.\n\n\n<details>\n  <summary>Changelog</summary>\n  \n  \n   ### 1.15.0\n   ```\n   ==========================\n\nNumPy 1.15.0 is a release with an unusual number of cleanups, many deprecations\nof old functions, and improvements to many existing functions. Please read the\ndetailed descriptions below to see if you are affected.\n\nFor testing, we have switched to pytest as a replacement for the no longer\nmaintained nose framework. The old nose based interface remains for downstream\nprojects who may still be using it.\n\nThe Python versions supported by this release are 2.7, 3.4-3.7. The wheels are\nlinked with OpenBLAS v0.3.0, which should fix some of the linalg problems\nreported for NumPy 1.14.\n\n\nHighlights\n==========\n\n* NumPy has switched to pytest for testing.\n* A new  `numpy.printoptions` context manager.\n* Many improvements to the histogram functions.\n* Support for unicode field names in python 2.7.\n* Improved support for PyPy.\n* Fixes and improvements to `numpy.einsum`.\n\n\nNew functions\n=============\n\n* `numpy.gcd` and `numpy.lcm`, to compute the greatest common divisor and least\n  common multiple.\n\n* `numpy.ma.stack`, the `numpy.stack` array-joining function generalized to\n  masked arrays.\n\n* `numpy.quantile` function, an interface to ``percentile`` without factors of\n  100\n\n* `numpy.nanquantile` function, an interface to ``nanpercentile`` without\n  factors of 100\n\n* `numpy.printoptions`, a context manager that sets print options temporarily\n  for the scope of the ``with`` block::\n\n    &gt;&gt;&gt; with np.printoptions(precision=2):\n    ...     print(np.array([2.0]) / 3)\n    [0.67]\n\n* `numpy.histogram_bin_edges`, a function to get the edges of the bins used by a\n  histogram without needing to calculate the histogram.\n\n* C functions `npy_get_floatstatus_barrier` and `npy_clear_floatstatus_barrier`\n  have been added to deal with compiler optimization changing the order of\n  operations.  See below for details.\n\n\nDeprecations\n============\n\n* Aliases of builtin `pickle` functions are deprecated, in favor of their\n  unaliased ``pickle.&lt;func&gt;`` names:\n\n  * `numpy.loads`\n  * `numpy.core.numeric.load`\n  * `numpy.core.numeric.loads`\n  * `numpy.ma.loads`, `numpy.ma.dumps`\n  * `numpy.ma.load`, `numpy.ma.dump` - these functions already failed on\n    python 3 when called with a string.\n\n* Multidimensional indexing with anything but a tuple is deprecated. This means\n  that the index list in ``ind = [slice(None), 0]; arr[ind]`` should be changed\n  to a tuple, e.g., ``ind = [slice(None), 0]; arr[tuple(ind)]`` or\n  ``arr[(slice(None), 0)]``. That change is necessary to avoid ambiguity in\n  expressions such as ``arr[[[0, 1], [0, 1]]]``, currently interpreted as\n  ``arr[array([0, 1]), array([0, 1])]``, that will be interpreted\n  as ``arr[array([[0, 1], [0, 1]])]`` in the future.\n\n* Imports from the following sub-modules are deprecated, they will be removed\n  at some future date.\n\n  * `numpy.testing.utils`\n  * `numpy.testing.decorators`\n  * `numpy.testing.nosetester`\n  * `numpy.testing.noseclasses`\n  * `numpy.core.umath_tests`\n\n* Giving a generator to `numpy.sum` is now deprecated. This was undocumented\n  behavior, but worked. Previously, it would calculate the sum of the generator\n  expression.  In the future, it might return a different result. Use\n  ``np.sum(np.from_iter(generator))`` or the built-in Python ``sum`` instead.\n\n* Users of the C-API should call ``PyArrayResolveWriteBackIfCopy`` or\n  ``PyArray_DiscardWritbackIfCopy`` on any array with the ``WRITEBACKIFCOPY``\n  flag set, before deallocating the array. A deprecation warning will be\n  emitted if those calls are not used when needed.\n\n* Users of ``nditer`` should use the nditer object as a context manager\n  anytime one of the iterator operands is writeable, so that numpy can\n  manage writeback semantics, or should call ``it.close()``. A\n  `RuntimeWarning` may be emitted otherwise in these cases.\n\n* The ``normed`` argument of ``np.histogram``, deprecated long ago in 1.6.0,\n  now emits a ``DeprecationWarning``.\n\n\nFuture Changes\n==============\n\n* NumPy 1.16 will drop support for Python 3.4.\n* NumPy 1.17 will drop support for Python 2.7.\n\n\nCompatibility notes\n===================\n\nCompiled testing modules renamed and made private\n-------------------------------------------------\nThe following compiled modules have been renamed and made private:\n\n* ``umath_tests`` -&gt; ``_umath_tests``\n* ``test_rational`` -&gt; ``_rational_tests``\n* ``multiarray_tests`` -&gt; ``_multiarray_tests``\n* ``struct_ufunc_test`` -&gt; ``_struct_ufunc_tests``\n* ``operand_flag_tests`` -&gt; ``_operand_flag_tests``\n\nThe ``umath_tests`` module is still available for backwards compatibility, but\nwill be removed in the future.\n\nThe ``NpzFile`` returned by ``np.savez`` is now a ``collections.abc.Mapping``\n-----------------------------------------------------------------------------\nThis means it behaves like a readonly dictionary, and has a new ``.values()``\nmethod and ``len()`` implementation.\n\nFor python 3, this means that ``.iteritems()``, ``.iterkeys()`` have been\ndeprecated, and ``.keys()`` and ``.items()`` now return views and not lists.\nThis is consistent with how the builtin ``dict`` type changed between python 2\nand python 3.\n\nUnder certain conditions, ``nditer`` must be used in a context manager\n----------------------------------------------------------------------\nWhen using an `numpy.nditer` with the ``&quot;writeonly&quot;`` or ``&quot;readwrite&quot;`` flags, there\nare some circumstances where nditer doesn&#39;t actually give you a view of the\nwritable array. Instead, it gives you a copy, and if you make changes to the\ncopy, nditer later writes those changes back into your actual array. Currently,\nthis writeback occurs when the array objects are garbage collected, which makes\nthis API error-prone on CPython and entirely broken on PyPy. Therefore,\n``nditer`` should now be used as a context manager whenever it is used\nwith writeable arrays, e.g., ``with np.nditer(...) as it: ...``. You may also\nexplicitly call ``it.close()`` for cases where a context manager is unusable,\nfor instance in generator expressions.\n\nNumpy has switched to using pytest instead of nose for testing\n--------------------------------------------------------------\nThe last nose release was 1.3.7 in June, 2015, and development of that tool has\nended, consequently NumPy has now switched to using pytest. The old decorators\nand nose tools that were previously used by some downstream projects remain\navailable, but will not be maintained. The standard testing utilities,\n``assert_almost_equal`` and such, are not be affected by this change except for\nthe nose specific functions ``import_nose`` and ``raises``. Those functions are\nnot used in numpy, but are kept for downstream compatibility.\n\nNumpy no longer monkey-patches ``ctypes`` with ``__array_interface__``\n----------------------------------------------------------------------\nPreviously numpy added ``__array_interface__`` attributes to all the integer\ntypes from ``ctypes``.\n\n``np.ma.notmasked_contiguous`` and ``np.ma.flatnotmasked_contiguous`` always return lists\n-----------------------------------------------------------------------------------------\nThis is the documented behavior, but previously the result could be any of\nslice, None, or list.\n\nAll downstream users seem to check for the ``None`` result from\n``flatnotmasked_contiguous`` and replace it with ``[]``.  Those callers will\ncontinue to work as before.\n\n``np.squeeze`` restores old behavior of objects that cannot handle an ``axis`` argument\n---------------------------------------------------------------------------------------\nPrior to version ``1.7.0``, `numpy.squeeze` did not have an ``axis`` argument and\nall empty axes were removed by default. The incorporation of an ``axis``\nargument made it possible to selectively squeeze single or multiple empty axes,\nbut the old API expectation was not respected because axes could still be\nselectively removed (silent success) from an object expecting all empty axes to\nbe removed. That silent, selective removal of empty axes for objects expecting\nthe old behavior has been fixed and the old behavior restored.\n\nunstructured void array&#39;s ``.item`` method now returns a bytes object\n---------------------------------------------------------------------\n``.item`` now returns a ``bytes`` object instead of a buffer or byte array.\nThis may affect code which assumed the return value was mutable, which is no\nlonger the case.\n\n``copy.copy`` and ``copy.deepcopy`` no longer turn ``masked`` into an array\n---------------------------------------------------------------------------\nSince ``np.ma.masked`` is a readonly scalar, copying should be a no-op. These\nfunctions now behave consistently with ``np.copy()``.\n\nMultifield Indexing of Structured Arrays will still return a copy\n-----------------------------------------------------------------\nThe change that multi-field indexing of structured arrays returns a view\ninstead of a copy is pushed back to 1.16. A new method\n``numpy.lib.recfunctions.repack_fields`` has been introduced to help mitigate\nthe effects of this change, which can be used to write code compatible with\nboth numpy 1.15 and 1.16. For more information on how to update code to account\nfor this future change see the &quot;accessing multiple fields&quot; section of the\n`user guide &lt;https://docs.scipy.org/doc/numpy/user/basics.rec.html&gt;`__.\n\n\nC API changes\n=============\n\nNew functions ``npy_get_floatstatus_barrier`` and ``npy_clear_floatstatus_barrier``\n-----------------------------------------------------------------------------------\nFunctions ``npy_get_floatstatus_barrier`` and ``npy_clear_floatstatus_barrier``\nhave been added and should be used in place of the ``npy_get_floatstatus``and\n``npy_clear_status`` functions. Optimizing compilers like GCC 8.1 and Clang\nwere rearranging the order of operations when the previous functions were used\nin the ufunc SIMD functions, resulting in the floatstatus flags being checked\nbefore the operation whose status we wanted to check was run.  See `10339\n&lt;https://github.com/numpy/numpy/issues/10370&gt;`__.\n\nChanges to ``PyArray_GetDTypeTransferFunction``\n-----------------------------------------------\n``PyArray_GetDTypeTransferFunction`` now defaults to using user-defined\n``copyswapn`` / ``copyswap`` for user-defined dtypes. If this causes a\nsignificant performance hit, consider implementing ``copyswapn`` to reflect the\nimplementation of ``PyArray_GetStridedCopyFn``.  See `10898\n&lt;https://github.com/numpy/numpy/pull/10898&gt;`__.\n\n\nNew Features\n============\n\n``np.gcd`` and ``np.lcm`` ufuncs added for integer and objects types\n--------------------------------------------------------------------\nThese compute the greatest common divisor, and lowest common multiple,\nrespectively. These work on all the numpy integer types, as well as the\nbuiltin arbitrary-precision ``Decimal`` and ``long`` types.\n\nSupport for cross-platform builds for iOS\n-----------------------------------------\nThe build system has been modified to add support for the\n``_PYTHON_HOST_PLATFORM`` environment variable, used by ``distutils`` when\ncompiling on one platform for another platform. This makes it possible to\ncompile NumPy for iOS targets.\n\nThis only enables you to compile NumPy for one specific platform at a time.\nCreating a full iOS-compatible NumPy package requires building for the 5\narchitectures supported by iOS (i386, x86_64, armv7, armv7s and arm64), and\ncombining these 5 compiled builds products into a single &quot;fat&quot; binary.\n\n``return_indices`` keyword added for ``np.intersect1d``\n-------------------------------------------------------\nNew keyword ``return_indices`` returns the indices of the two input arrays\nthat correspond to the common elements.\n\n``np.quantile`` and ``np.nanquantile``\n--------------------------------------\nLike ``np.percentile`` and ``np.nanpercentile``, but takes quantiles in [0, 1]\nrather than percentiles in [0, 100]. ``np.percentile`` is now a thin wrapper\naround ``np.quantile`` with the extra step of dividing by 100.\n\n\nBuild system\n------------\nAdded experimental support for the 64-bit RISC-V architecture.\n\n\nImprovements\n============\n\n``np.einsum`` updates\n---------------------\nSyncs einsum path optimization tech between `numpy` and `opt_einsum`. In\nparticular, the `greedy` path has received many enhancements by jcmgray. A\nfull list of issues fixed are:\n\n* Arbitrary memory can be passed into the `greedy` path. Fixes gh-11210.\n* The greedy path has been updated to contain more dynamic programming ideas\n  preventing a large number of duplicate (and expensive) calls that figure out\n  the actual pair contraction that takes place. Now takes a few seconds on\n  several hundred input tensors. Useful for matrix product state theories.\n* Reworks the broadcasting dot error catching found in gh-11218 gh-10352 to be\n  a bit earlier in the process.\n* Enhances the `can_dot` functionality that previous missed an edge case (part\n  of gh-11308).\n\n``np.ufunc.reduce`` and related functions now accept an initial value\n---------------------------------------------------------------------\n``np.ufunc.reduce``, ``np.sum``, ``np.prod``, ``np.min`` and ``np.max`` all\nnow accept an ``initial`` keyword argument that specifies the value to start\nthe reduction with.\n\n``np.flip`` can operate over multiple axes\n------------------------------------------\n``np.flip`` now accepts None, or tuples of int, in its ``axis`` argument. If\naxis is None, it will flip over all the axes.\n\n``histogram`` and ``histogramdd`` functions have moved to ``np.lib.histograms``\n-------------------------------------------------------------------------------\nThese were originally found in ``np.lib.function_base``. They are still\navailable under their un-scoped ``np.histogram(dd)`` names, and\nto maintain compatibility, aliased at ``np.lib.function_base.histogram(dd)``.\n\nCode that does ``from np.lib.function_base import *`` will need to be updated\nwith the new location, and should consider not using ``import *`` in future.\n\n``histogram`` will accept NaN values when explicit bins are given\n-----------------------------------------------------------------\nPreviously it would fail when trying to compute a finite range for the data.\nSince the range is ignored anyway when the bins are given explicitly, this error\nwas needless.\n\nNote that calling ``histogram`` on NaN values continues to raise the\n``RuntimeWarning`` s typical of working with nan values, which can be silenced\nas usual with ``errstate``.\n\n``histogram`` works on datetime types, when explicit bin edges are given\n------------------------------------------------------------------------\nDates, times, and timedeltas can now be histogrammed. The bin edges must be\npassed explicitly, and are not yet computed automatically.\n\n``histogram`` &quot;auto&quot; estimator handles limited variance better\n--------------------------------------------------------------\nNo longer does an IQR of 0 result in ``n_bins=1``, rather the number of bins\nchosen is related to the data size in this situation.\n\nThe edges retuned by `histogram`` and ``histogramdd`` now match the data float type\n-----------------------------------------------------------------------------------\nWhen passed ``np.float16``, ``np.float32``, or ``np.longdouble`` data, the\nreturned edges are now of the same dtype. Previously, ``histogram`` would only\nreturn the same type if explicit bins were given, and ``histogram`` would\nproduce ``float64`` bins no matter what the inputs.\n\n``histogramdd`` allows explicit ranges to be given in a subset of axes\n----------------------------------------------------------------------\nThe ``range`` argument of `numpy.histogramdd` can now contain ``None`` values to\nindicate that the range for the corresponding axis should be computed from the\ndata. Previously, this could not be specified on a per-axis basis.\n\nThe normed arguments of ``histogramdd`` and ``histogram2d`` have been renamed\n-----------------------------------------------------------------------------\nThese arguments are now called ``density``, which is consistent with\n``histogram``. The old argument continues to work, but the new name should be\npreferred.\n\n``np.r_`` works with 0d arrays, and ``np.ma.mr_`` works with ``np.ma.masked``\n-----------------------------------------------------------------------------\n0d arrays passed to the `r_` and `mr_` concatenation helpers are now treated as\nthough they are arrays of length 1. Previously, passing these was an error.\nAs a result, `numpy.ma.mr_` now works correctly on the ``masked`` constant.\n\n``np.ptp`` accepts a ``keepdims`` argument, and extended axis tuples\n--------------------------------------------------------------------\n``np.ptp`` (peak-to-peak) can now work over multiple axes, just like ``np.max``\nand ``np.min``.\n\n``MaskedArray.astype`` now is identical to ``ndarray.astype``\n-------------------------------------------------------------\nThis means it takes all the same arguments, making more code written for\nndarray work for masked array too.\n\nEnable AVX2/AVX512 at compile time\n----------------------------------\nChange to simd.inc.src to allow use of AVX2 or AVX512 at compile time. Previously\ncompilation for avx2 (or 512) with -march=native would still use the SSE\ncode for the simd functions even when the rest of the code got AVX2.\n\n``nan_to_num`` always returns scalars when receiving scalar or 0d inputs\n------------------------------------------------------------------------\nPreviously an array was returned for integer scalar inputs, which is\ninconsistent with the behavior for float inputs, and that of ufuncs in general.\nFor all types of scalar or 0d input, the result is now a scalar.\n\n``np.flatnonzero`` works on numpy-convertible types\n---------------------------------------------------\n``np.flatnonzero`` now uses ``np.ravel(a)`` instead of ``a.ravel()``, so it\nworks for lists, tuples, etc.\n\n``np.interp`` returns numpy scalars rather than builtin scalars\n---------------------------------------------------------------\nPreviously ``np.interp(0.5, [0, 1], [10, 20])`` would return a ``float``, but\nnow it returns a ``np.float64`` object, which more closely matches the behavior\nof other functions.\n\nAdditionally, the special case of ``np.interp(object_array_0d, ...)`` is no\nlonger supported, as ``np.interp(object_array_nd)`` was never supported anyway.\n\nAs a result of this change, the ``period`` argument can now be used on 0d\narrays.\n\nAllow dtype field names to be unicode in Python 2\n-------------------------------------------------\nPreviously ``np.dtype([(u&#39;name&#39;, float)])`` would raise a ``TypeError`` in\nPython 2, as only bytestrings were allowed in field names. Now any unicode\nstring field names will be encoded with the ``ascii`` codec, raising a\n``UnicodeEncodeError`` upon failure.\n\nThis change makes it easier to write Python 2/3 compatible code using\n``from __future__ import unicode_literals``, which previously would cause\nstring literal field names to raise a TypeError in Python 2.\n\nComparison ufuncs accept ``dtype=object``, overriding the default ``bool``\n--------------------------------------------------------------------------\nThis allows object arrays of symbolic types, which override ``==`` and other\noperators to return expressions, to be compared elementwise with\n``np.equal(a, b, dtype=object)``.\n\n``sort`` functions accept ``kind=&#39;stable&#39;``\n-------------------------------------------\nUp until now, to perform a stable sort on the data, the user must do:\n\n    &gt;&gt;&gt; np.sort([5, 2, 6, 2, 1], kind=&#39;mergesort&#39;)\n    [1, 2, 2, 5, 6]\n\nbecause merge sort is the only stable sorting algorithm available in\nNumPy. However, having kind=&#39;mergesort&#39; does not make it explicit that\nthe user wants to perform a stable sort thus harming the readability.\n\nThis change allows the user to specify kind=&#39;stable&#39; thus clarifying\nthe intent.\n\nDo not make temporary copies for in-place accumulation\n------------------------------------------------------\nWhen ufuncs perform accumulation they no longer make temporary copies because\nof the overlap between input an output, that is, the next element accumulated\nis added before the accumulated result is stored in its place, hence the\noverlap is safe. Avoiding the copy results in faster execution.\n\n``linalg.matrix_power`` can now handle stacks of matrices\n---------------------------------------------------------\nLike other functions in ``linalg``, ``matrix_power`` can now deal with arrays\nof dimension larger than 2, which are treated as stacks of matrices. As part\nof the change, to further improve consistency, the name of the first argument\nhas been changed to ``a`` (from ``M``), and the exceptions for non-square\nmatrices have been changed to ``LinAlgError`` (from ``ValueError``).\n\nIncreased performance in ``random.permutation`` for multidimensional arrays\n---------------------------------------------------------------------------\n``permutation`` uses the fast path in ``random.shuffle`` for all input\narray dimensions.  Previously the fast path was only used for 1-d arrays.\n\nGeneralized ufuncs now accept ``axes``, ``axis`` and ``keepdims`` arguments\n---------------------------------------------------------------------------\nOne can control over which axes a generalized ufunc operates by passing in an\n``axes`` argument, a list of tuples with indices of particular axes.  For\ninstance, for a signature of ``(i,j),(j,k)-&gt;(i,k)`` appropriate for matrix\nmultiplication, the base elements are two-dimensional matrices and these are\ntaken to be stored in the two last axes of each argument.  The corresponding\naxes keyword would be ``[(-2, -1), (-2, -1), (-2, -1)]``. If one wanted to\nuse leading dimensions instead, one would pass in ``[(0, 1), (0, 1), (0, 1)]``.\n\nFor simplicity, for generalized ufuncs that operate on 1-dimensional arrays\n(vectors), a single integer is accepted instead of a single-element tuple, and\nfor generalized ufuncs for which all outputs are scalars, the (empty) output\ntuples can be omitted.  Hence, for a signature of ``(i),(i)-&gt;()`` appropriate\nfor an inner product, one could pass in ``axes=[0, 0]`` to indicate that the\nvectors are stored in the first dimensions of the two inputs arguments.\n\nAs a short-cut for generalized ufuncs that are similar to reductions, i.e.,\nthat act on a single, shared core dimension such as the inner product example\nabove, one can pass an ``axis`` argument. This is equivalent to passing in\n``axes`` with identical entries for all arguments with that core dimension\n(e.g., for the example above, ``axes=[(axis,), (axis,)]``).\n\nFurthermore, like for reductions, for generalized ufuncs that have inputs that\nall have the same number of core dimensions and outputs with no core dimension,\none can pass in ``keepdims`` to leave a dimension with size 1 in the outputs,\nthus allowing proper broadcasting against the original inputs. The location of\nthe extra dimension can be controlled with ``axes``. For instance, for the\ninner-product example, ``keepdims=True, axes=[-2, -2, -2]`` would act on the\ninner-product example, ``keepdims=True, axis=-2`` would act on the\none-but-last dimension of the input arguments, and leave a size 1 dimension in\nthat place in the output.\n\nfloat128 values now print correctly on ppc systems\n--------------------------------------------------\nPreviously printing float128 values was buggy on ppc, since the special\ndouble-double floating-point-format on these systems was not accounted for.\nfloat128s now print with correct rounding and uniqueness.\n\nWarning to ppc users: You should upgrade glibc if it is version &lt;=2.23,\nespecially if using float128. On ppc, glibc&#39;s malloc in these version often\nmisaligns allocated memory which can crash numpy when using float128 values.\n\nNew ``np.take_along_axis`` and ``np.put_along_axis`` functions\n--------------------------------------------------------------\nWhen used on multidimensional arrays, ``argsort``, ``argmin``, ``argmax``, and\n``argpartition`` return arrays that are difficult to use as indices.\n``take_along_axis`` provides an easy way to use these indices to lookup values\nwithin an array, so that::\n\n    np.take_along_axis(a, np.argsort(a, axis=axis), axis=axis)\n\nis the same as::\n\n    np.sort(a, axis=axis)\n\n``np.put_along_axis`` acts as the dual operation for writing to these indices\nwithin an array.\n\n\n\n=========================\n   ```\n   \n  \n  \n   ### 1.14.5\n   ```\n   ==========================\n\nThis is a bugfix release for bugs reported following the 1.14.4 release. The\nmost significant fixes are:\n\n* fixes for compilation errors on alpine and NetBSD\n\nThe Python versions supported in this release are 2.7 and 3.4 - 3.6. The Python\n3.6 wheels available from PIP are built with Python 3.6.2 and should be\ncompatible with all previous versions of Python 3.6. The source releases were\ncythonized with Cython 0.28.2 and should work for the upcoming Python 3.7.\n\nContributors\n============\n\nA total of 1 person contributed to this release.  People with a &quot;+&quot; by their\nnames contributed a patch for the first time.\n\n* Charles Harris\n\nPull requests merged\n====================\n\nA total of 2 pull requests were merged for this release.\n\n* `11274 &lt;https://github.com/numpy/numpy/pull/11274&gt;`__: BUG: Correct use of NPY_UNUSED.\n* `11294 &lt;https://github.com/numpy/numpy/pull/11294&gt;`__: BUG: Remove extra trailing parentheses.\n\n\n\n=========================\n   ```\n   \n  \n  \n   ### 1.14.4\n   ```\n   ==========================\n\nThis is a bugfix release for bugs reported following the 1.14.3 release. The\nmost significant fixes are:\n\n* fixes for compiler instruction reordering that resulted in NaN&#39;s not being\n  properly propagated in `np.max` and `np.min`,\n\n* fixes for bus faults on SPARC and older ARM due to incorrect alignment\n  checks.\n\nThere are also improvements to printing of long doubles on PPC platforms. All\nis not yet perfect on that platform, the whitespace padding is still incorrect\nand is to be fixed in numpy 1.15, consequently NumPy still fails some\nprinting-related (and other) unit tests on ppc systems. However, the printed\nvalues are now correct.\n\nNote that NumPy will error on import if it detects incorrect float32 `dot`\nresults. This problem has been seen on the Mac when working in the Anaconda\nenviroment and is due to a subtle interaction between MKL and PyQt5.  It is not\nstrictly a NumPy problem, but it is best that users be aware of it.  See the\ngh-8577 NumPy issue for more information.\n\nThe Python versions supported in this release are 2.7 and 3.4 - 3.6. The Python\n3.6 wheels available from PIP are built with Python 3.6.2 and should be\ncompatible with all previous versions of Python 3.6. The source releases were\ncythonized with Cython 0.28.2 and should work for the upcoming Python 3.7.\n\nContributors\n============\n\nA total of 7 people contributed to this release.  People with a &quot;+&quot; by their\nnames contributed a patch for the first time.\n\n* Allan Haldane\n* Charles Harris\n* Marten van Kerkwijk\n* Matti Picus\n* Pauli Virtanen\n* Ryan Soklaski +\n* Sebastian Berg\n\nPull requests merged\n====================\n\nA total of 11 pull requests were merged for this release.\n\n* `11104 &lt;https://github.com/numpy/numpy/pull/11104&gt;`__: BUG: str of DOUBLE_DOUBLE format wrong on ppc64\n* `11170 &lt;https://github.com/numpy/numpy/pull/11170&gt;`__: TST: linalg: add regression test for gh-8577\n* `11174 &lt;https://github.com/numpy/numpy/pull/11174&gt;`__: MAINT: add sanity-checks to be run at import time\n* `11181 &lt;https://github.com/numpy/numpy/pull/11181&gt;`__: BUG: void dtype setup checked offset not actual pointer for alignment\n* `11194 &lt;https://github.com/numpy/numpy/pull/11194&gt;`__: BUG: Python2 doubles don&#39;t print correctly in interactive shell.\n* `11198 &lt;https://github.com/numpy/numpy/pull/11198&gt;`__: BUG: optimizing compilers can reorder call to npy_get_floatstatus\n* `11199 &lt;https://github.com/numpy/numpy/pull/11199&gt;`__: BUG: reduce using SSE only warns if inside SSE loop\n* `11203 &lt;https://github.com/numpy/numpy/pull/11203&gt;`__: BUG: Bytes delimiter/comments in genfromtxt should be decoded\n* `11211 &lt;https://github.com/numpy/numpy/pull/11211&gt;`__: BUG: Fix reference count/memory leak exposed by better testing\n* `11219 &lt;https://github.com/numpy/numpy/pull/11219&gt;`__: BUG: Fixes einsum broadcasting bug when optimize=True\n* `11251 &lt;https://github.com/numpy/numpy/pull/11251&gt;`__: DOC: Document 1.14.4 release.\n\n\n==========================\n   ```\n   \n  \n  \n   ### 1.14.3\n   ```\n   ==========================\n\nThis is a bugfix release for a few bugs reported following the 1.14.2 release:\n\n* np.lib.recfunctions.fromrecords accepts a list-of-lists, until 1.15\n* In python2, float types use the new print style when printing to a file\n* style arg in &quot;legacy&quot; print mode now works for 0d arrays\n\nThe Python versions supported in this release are 2.7 and 3.4 - 3.6. The Python\n3.6 wheels available from PIP are built with Python 3.6.2 and should be\ncompatible with all previous versions of Python 3.6. The source releases were\ncythonized with Cython 0.28.2.\n\nContributors\n============\n\nA total of 6 people contributed to this release.  People with a &quot;+&quot; by their\nnames contributed a patch for the first time.\n\n* Allan Haldane\n* Charles Harris\n* Jonathan March +\n* Malcolm Smith +\n* Matti Picus\n* Pauli Virtanen\n\nPull requests merged\n====================\n\nA total of 8 pull requests were merged for this release.\n\n* `10862 &lt;https://github.com/numpy/numpy/pull/10862&gt;`__: BUG: floating types should override tp_print (1.14 backport)\n* `10905 &lt;https://github.com/numpy/numpy/pull/10905&gt;`__: BUG: for 1.14 back-compat, accept list-of-lists in fromrecords\n* `10947 &lt;https://github.com/numpy/numpy/pull/10947&gt;`__: BUG: &#39;style&#39; arg to array2string broken in legacy mode (1.14...\n* `10959 &lt;https://github.com/numpy/numpy/pull/10959&gt;`__: BUG: test, fix for missing flags[&#39;WRITEBACKIFCOPY&#39;] key\n* `10960 &lt;https://github.com/numpy/numpy/pull/10960&gt;`__: BUG: Add missing underscore to prototype in check_embedded_lapack\n* `10961 &lt;https://github.com/numpy/numpy/pull/10961&gt;`__: BUG: Fix encoding regression in ma/bench.py (Issue 10868)\n* `10962 &lt;https://github.com/numpy/numpy/pull/10962&gt;`__: BUG: core: fix NPY_TITLE_KEY macro on pypy\n* `10974 &lt;https://github.com/numpy/numpy/pull/10974&gt;`__: BUG: test, fix PyArray_DiscardWritebackIfCopy...\n\n\n=========================\n   ```\n   \n  \n</details>\n\n\n \n\n<details>\n  <summary>Links</summary>\n  \n  - PyPI: https://pypi.org/project/numpy\n  - Changelog: https://pyup.io/changelogs/numpy/\n  - Homepage: http://www.numpy.org\n</details>\n\n\n\n\n\n","created_at":"2018-09-03T17:32:15Z","updated_at":"2018-09-10T17:34:21Z","closed_at":"2018-09-10T17:34:21Z","merged_at":null,"merge_commit_sha":"ef06ae15f36cdeaa0bd523fa1eb62aa8f57c87e4","assignee":null,"assignees":[],"requested_reviewers":[],"requested_teams":[],"labels":[],"milestone":null,"commits_url":"https://api.github.com/repos/pyros-dev/rostful/pulls/138/commits","review_comments_url":"https://api.github.com/repos/pyros-dev/rostful/pulls/138/comments","review_comment_url":"https://api.github.com/repos/pyros-dev/rostful/pulls/comments{/number}","comments_url":"https://api.github.com/repos/pyros-dev/rostful/issues/138/comments","statuses_url":"https://api.github.com/repos/pyros-dev/rostful/statuses/bbdded868dbdc3fede4c127e1bebfbf0d8a0040c","head":{"label":"pyros-dev:pyup/scheduled-update-2018-09-03","ref":"pyup/scheduled-update-2018-09-03","sha":"bbdded868dbdc3fede4c127e1bebfbf0d8a0040c","user":{"login":"pyros-dev","id":30517820,"node_id":"MDEyOk9yZ2FuaXphdGlvbjMwNTE3ODIw","avatar_url":"https://avatars2.githubusercontent.com/u/30517820?v=4","gravatar_id":"","url":"https://api.github.com/users/pyros-dev","html_url":"https://github.com/pyros-dev","followers_url":"https://api.github.com/users/pyros-dev/followers","following_url":"https://api.github.com/users/pyros-dev/following{/other_user}","gists_url":"https://api.github.com/users/pyros-dev/gists{/gist_id}","starred_url":"https://api.github.com/users/pyros-dev/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/pyros-dev/subscriptions","organizations_url":"https://api.github.com/users/pyros-dev/orgs","repos_url":"https://api.github.com/users/pyros-dev/repos","events_url":"https://api.github.com/users/pyros-dev/events{/privacy}","received_events_url":"https://api.github.com/users/pyros-dev/received_events","type":"Organization","site_admin":false},"repo":{"id":33977640,"node_id":"MDEwOlJlcG9zaXRvcnkzMzk3NzY0MA==","name":"rostful","full_name":"pyros-dev/rostful","owner":{"login":"pyros-dev","id":30517820,"node_id":"MDEyOk9yZ2FuaXphdGlvbjMwNTE3ODIw","avatar_url":"https://avatars2.githubusercontent.com/u/30517820?v=4","gravatar_id":"","url":"https://api.github.com/users/pyros-dev","html_url":"https://github.com/pyros-dev","followers_url":"https://api.github.com/users/pyros-dev/followers","following_url":"https://api.github.com/users/pyros-dev/following{/other_user}","gists_url":"https://api.github.com/users/pyros-dev/gists{/gist_id}","starred_url":"https://api.github.com/users/pyros-dev/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/pyros-dev/subscriptions","organizations_url":"https://api.github.com/users/pyros-dev/orgs","repos_url":"https://api.github.com/users/pyros-dev/repos","events_url":"https://api.github.com/users/pyros-dev/events{/privacy}","received_events_url":"https://api.github.com/users/pyros-dev/received_events","type":"Organization","site_admin":false},"private":false,"html_url":"https://github.com/pyros-dev/rostful","description":"A lightweight package for providing and consuming ROS services, actions, and topics as RESTful web services","fork":false,"url":"https://api.github.com/repos/pyros-dev/rostful","forks_url":"https://api.github.com/repos/pyros-dev/rostful/forks","keys_url":"https://api.github.com/repos/pyros-dev/rostful/keys{/key_id}","collaborators_url":"https://api.github.com/repos/pyros-dev/rostful/collaborators{/collaborator}","teams_url":"https://api.github.com/repos/pyros-dev/rostful/teams","hooks_url":"https://api.github.com/repos/pyros-dev/rostful/hooks","issue_events_url":"https://api.github.com/repos/pyros-dev/rostful/issues/events{/number}","events_url":"https://api.github.com/repos/pyros-dev/rostful/events","assignees_url":"https://api.github.com/repos/pyros-dev/rostful/assignees{/user}","branches_url":"https://api.github.com/repos/pyros-dev/rostful/branches{/branch}","tags_url":"https://api.github.com/repos/pyros-dev/rostful/tags","blobs_url":"https://api.github.com/repos/pyros-dev/rostful/git/blobs{/sha}","git_tags_url":"https://api.github.com/repos/pyros-dev/rostful/git/tags{/sha}","git_refs_url":"https://api.github.com/repos/pyros-dev/rostful/git/refs{/sha}","trees_url":"https://api.github.com/repos/pyros-dev/rostful/git/trees{/sha}","statuses_url":"https://api.github.com/repos/pyros-dev/rostful/statuses/{sha}","languages_url":"https://api.github.com/repos/pyros-dev/rostful/languages","stargazers_url":"https://api.github.com/repos/pyros-dev/rostful/stargazers","contributors_url":"https://api.github.com/repos/pyros-dev/rostful/contributors","subscribers_url":"https://api.github.com/repos/pyros-dev/rostful/subscribers","subscription_url":"https://api.github.com/repos/pyros-dev/rostful/subscription","commits_url":"https://api.github.com/repos/pyros-dev/rostful/commits{/sha}","git_commits_url":"https://api.github.com/repos/pyros-dev/rostful/git/commits{/sha}","comments_url":"https://api.github.com/repos/pyros-dev/rostful/comments{/number}","issue_comment_url":"https://api.github.com/repos/pyros-dev/rostful/issues/comments{/number}","contents_url":"https://api.github.com/repos/pyros-dev/rostful/contents/{+path}","compare_url":"https://api.github.com/repos/pyros-dev/rostful/compare/{base}...{head}","merges_url":"https://api.github.com/repos/pyros-dev/rostful/merges","archive_url":"https://api.github.com/repos/pyros-dev/rostful/{archive_format}{/ref}","downloads_url":"https://api.github.com/repos/pyros-dev/rostful/downloads","issues_url":"https://api.github.com/repos/pyros-dev/rostful/issues{/number}","pulls_url":"https://api.github.com/repos/pyros-dev/rostful/pulls{/number}","milestones_url":"https://api.github.com/repos/pyros-dev/rostful/milestones{/number}","notifications_url":"https://api.github.com/repos/pyros-dev/rostful/notifications{?since,all,participating}","labels_url":"https://api.github.com/repos/pyros-dev/rostful/labels{/name}","releases_url":"https://api.github.com/repos/pyros-dev/rostful/releases{/id}","deployments_url":"https://api.github.com/repos/pyros-dev/rostful/deployments","created_at":"2015-04-15T06:40:06Z","updated_at":"2018-08-08T17:27:31Z","pushed_at":"2018-09-10T17:34:15Z","git_url":"git://github.com/pyros-dev/rostful.git","ssh_url":"git@github.com:pyros-dev/rostful.git","clone_url":"https://github.com/pyros-dev/rostful.git","svn_url":"https://github.com/pyros-dev/rostful","homepage":"","size":1227,"stargazers_count":26,"watchers_count":26,"language":"JavaScript","has_issues":true,"has_projects":true,"has_downloads":true,"has_wiki":true,"has_pages":false,"forks_count":20,"mirror_url":null,"archived":false,"open_issues_count":62,"license":null,"forks":20,"open_issues":62,"watchers":26,"default_branch":"master"}},"base":{"label":"pyros-dev:master","ref":"master","sha":"e607f63419a40420604e2286ddaa661b0862d167","user":{"login":"pyros-dev","id":30517820,"node_id":"MDEyOk9yZ2FuaXphdGlvbjMwNTE3ODIw","avatar_url":"https://avatars2.githubusercontent.com/u/30517820?v=4","gravatar_id":"","url":"https://api.github.com/users/pyros-dev","html_url":"https://github.com/pyros-dev","followers_url":"https://api.github.com/users/pyros-dev/followers","following_url":"https://api.github.com/users/pyros-dev/following{/other_user}","gists_url":"https://api.github.com/users/pyros-dev/gists{/gist_id}","starred_url":"https://api.github.com/users/pyros-dev/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/pyros-dev/subscriptions","organizations_url":"https://api.github.com/users/pyros-dev/orgs","repos_url":"https://api.github.com/users/pyros-dev/repos","events_url":"https://api.github.com/users/pyros-dev/events{/privacy}","received_events_url":"https://api.github.com/users/pyros-dev/received_events","type":"Organization","site_admin":false},"repo":{"id":33977640,"node_id":"MDEwOlJlcG9zaXRvcnkzMzk3NzY0MA==","name":"rostful","full_name":"pyros-dev/rostful","owner":{"login":"pyros-dev","id":30517820,"node_id":"MDEyOk9yZ2FuaXphdGlvbjMwNTE3ODIw","avatar_url":"https://avatars2.githubusercontent.com/u/30517820?v=4","gravatar_id":"","url":"https://api.github.com/users/pyros-dev","html_url":"https://github.com/pyros-dev","followers_url":"https://api.github.com/users/pyros-dev/followers","following_url":"https://api.github.com/users/pyros-dev/following{/other_user}","gists_url":"https://api.github.com/users/pyros-dev/gists{/gist_id}","starred_url":"https://api.github.com/users/pyros-dev/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/pyros-dev/subscriptions","organizations_url":"https://api.github.com/users/pyros-dev/orgs","repos_url":"https://api.github.com/users/pyros-dev/repos","events_url":"https://api.github.com/users/pyros-dev/events{/privacy}","received_events_url":"https://api.github.com/users/pyros-dev/received_events","type":"Organization","site_admin":false},"private":false,"html_url":"https://github.com/pyros-dev/rostful","description":"A lightweight package for providing and consuming ROS services, actions, and topics as RESTful web services","fork":false,"url":"https://api.github.com/repos/pyros-dev/rostful","forks_url":"https://api.github.com/repos/pyros-dev/rostful/forks","keys_url":"https://api.github.com/repos/pyros-dev/rostful/keys{/key_id}","collaborators_url":"https://api.github.com/repos/pyros-dev/rostful/collaborators{/collaborator}","teams_url":"https://api.github.com/repos/pyros-dev/rostful/teams","hooks_url":"https://api.github.com/repos/pyros-dev/rostful/hooks","issue_events_url":"https://api.github.com/repos/pyros-dev/rostful/issues/events{/number}","events_url":"https://api.github.com/repos/pyros-dev/rostful/events","assignees_url":"https://api.github.com/repos/pyros-dev/rostful/assignees{/user}","branches_url":"https://api.github.com/repos/pyros-dev/rostful/branches{/branch}","tags_url":"https://api.github.com/repos/pyros-dev/rostful/tags","blobs_url":"https://api.github.com/repos/pyros-dev/rostful/git/blobs{/sha}","git_tags_url":"https://api.github.com/repos/pyros-dev/rostful/git/tags{/sha}","git_refs_url":"https://api.github.com/repos/pyros-dev/rostful/git/refs{/sha}","trees_url":"https://api.github.com/repos/pyros-dev/rostful/git/trees{/sha}","statuses_url":"https://api.github.com/repos/pyros-dev/rostful/statuses/{sha}","languages_url":"https://api.github.com/repos/pyros-dev/rostful/languages","stargazers_url":"https://api.github.com/repos/pyros-dev/rostful/stargazers","contributors_url":"https://api.github.com/repos/pyros-dev/rostful/contributors","subscribers_url":"https://api.github.com/repos/pyros-dev/rostful/subscribers","subscription_url":"https://api.github.com/repos/pyros-dev/rostful/subscription","commits_url":"https://api.github.com/repos/pyros-dev/rostful/commits{/sha}","git_commits_url":"https://api.github.com/repos/pyros-dev/rostful/git/commits{/sha}","comments_url":"https://api.github.com/repos/pyros-dev/rostful/comments{/number}","issue_comment_url":"https://api.github.com/repos/pyros-dev/rostful/issues/comments{/number}","contents_url":"https://api.github.com/repos/pyros-dev/rostful/contents/{+path}","compare_url":"https://api.github.com/repos/pyros-dev/rostful/compare/{base}...{head}","merges_url":"https://api.github.com/repos/pyros-dev/rostful/merges","archive_url":"https://api.github.com/repos/pyros-dev/rostful/{archive_format}{/ref}","downloads_url":"https://api.github.com/repos/pyros-dev/rostful/downloads","issues_url":"https://api.github.com/repos/pyros-dev/rostful/issues{/number}","pulls_url":"https://api.github.com/repos/pyros-dev/rostful/pulls{/number}","milestones_url":"https://api.github.com/repos/pyros-dev/rostful/milestones{/number}","notifications_url":"https://api.github.com/repos/pyros-dev/rostful/notifications{?since,all,participating}","labels_url":"https://api.github.com/repos/pyros-dev/rostful/labels{/name}","releases_url":"https://api.github.com/repos/pyros-dev/rostful/releases{/id}","deployments_url":"https://api.github.com/repos/pyros-dev/rostful/deployments","created_at":"2015-04-15T06:40:06Z","updated_at":"2018-08-08T17:27:31Z","pushed_at":"2018-09-10T17:34:15Z","git_url":"git://github.com/pyros-dev/rostful.git","ssh_url":"git@github.com:pyros-dev/rostful.git","clone_url":"https://github.com/pyros-dev/rostful.git","svn_url":"https://github.com/pyros-dev/rostful","homepage":"","size":1227,"stargazers_count":26,"watchers_count":26,"language":"JavaScript","has_issues":true,"has_projects":true,"has_downloads":true,"has_wiki":true,"has_pages":false,"forks_count":20,"mirror_url":null,"archived":false,"open_issues_count":62,"license":null,"forks":20,"open_issues":62,"watchers":26,"default_branch":"master"}},"_links":{"self":{"href":"https://api.github.com/repos/pyros-dev/rostful/pulls/138"},"html":{"href":"https://github.com/pyros-dev/rostful/pull/138"},"issue":{"href":"https://api.github.com/repos/pyros-dev/rostful/issues/138"},"comments":{"href":"https://api.github.com/repos/pyros-dev/rostful/issues/138/comments"},"review_comments":{"href":"https://api.github.com/repos/pyros-dev/rostful/pulls/138/comments"},"review_comment":{"href":"https://api.github.com/repos/pyros-dev/rostful/pulls/comments{/number}"},"commits":{"href":"https://api.github.com/repos/pyros-dev/rostful/pulls/138/commits"},"statuses":{"href":"https://api.github.com/repos/pyros-dev/rostful/statuses/bbdded868dbdc3fede4c127e1bebfbf0d8a0040c"}},"author_association":"CONTRIBUTOR","merged":false,"mergeable":true,"rebaseable":true,"mergeable_state":"unstable","merged_by":null,"comments":1,"review_comments":0,"maintainer_can_modify":false,"commits":4,"additions":4,"deletions":4,"changed_files":1}}
{"actor":{"display_login":"pyup-bot"}}