{"action":"closed","number":82,"pull_request":{"url":"https://api.github.com/repos/nullart/freqtrade/pulls/82","id":217508641,"node_id":"MDExOlB1bGxSZXF1ZXN0MjE3NTA4NjQx","html_url":"https://github.com/nullart/freqtrade/pull/82","diff_url":"https://github.com/nullart/freqtrade/pull/82.diff","patch_url":"https://github.com/nullart/freqtrade/pull/82.patch","issue_url":"https://api.github.com/repos/nullart/freqtrade/issues/82","number":82,"state":"closed","locked":false,"title":"Scheduled daily dependency update on sunday","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 [ccxt](https://pypi.org/project/ccxt) from **1.15.42** to **1.17.341**.\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/ccxt\n  - Changelog: https://pyup.io/changelogs/ccxt/\n  - Homepage: https://ccxt.trade\n</details>\n\n\n\n\n\n### Update [SQLAlchemy](https://pypi.org/project/SQLAlchemy) from **1.2.9** to **1.2.12**.\n\n\n<details>\n  <summary>Changelog</summary>\n  \n  \n   ### 1.2.12\n   ```\n   :released: September 19, 2018\n\n    .. change::\n        :tags: bug, postgresql\n        :tickets: 4325\n\n        Fixed bug in PostgreSQL dialect where compiler keyword arguments such as\n        ``literal_binds=True`` were not being propagated to a DISTINCT ON\n        expression.\n\n    .. change::\n        :tags: bug, ext\n        :tickets: 4328\n\n        Fixed issue where :class:`.BakedQuery` did not include the specific query\n        class used by the :class:`.Session` as part of the cache key, leading to\n        incompatibilities when using custom query classes, in particular the\n        :class:`.ShardedQuery` which has some different argument signatures.\n\n    .. change::\n        :tags: bug, postgresql\n        :tickets: 4324\n\n        Fixed the :func:`.postgresql.array_agg` function, which is a slightly\n        altered version of the usual :func:`.functions.array_agg` function, to also\n        accept an incoming &quot;type&quot; argument without forcing an ARRAY around it,\n        essentially the same thing that was fixed for the generic function in 1.1\n        in :ticket:`4107`.\n\n    .. change::\n        :tags: bug, postgresql\n        :tickets: 4323\n\n        Fixed bug in PostgreSQL ENUM reflection where a case-sensitive, quoted name\n        would be reported by the query including quotes, which would not match a\n        target column during table reflection as the quotes needed to be stripped\n        off.\n\n\n    .. change::\n       :tags: bug, orm\n\n       Added a check within the weakref cleanup for the :class:`.InstanceState`\n       object to check for the presence of the ``dict`` builtin, in an effort to\n       reduce error messages generated when these cleanups occur during interpreter\n       shutdown.  Pull request courtesy Romuald Brunet.\n\n    .. change::\n        :tags: bug, orm, declarative\n        :tickets: 4326\n\n        Fixed bug where the declarative scan for attributes would receive the\n        expression proxy delivered by a hybrid attribute at the class level, and\n        not the hybrid attribute itself, when receiving the descriptor via the\n        ``declared_attr`` callable on a subclass of an already-mapped class. This\n        would lead to an attribute that did not report itself as a hybrid when\n        viewed within :attr:`.Mapper.all_orm_descriptors`.\n\n\n    .. change::\n        :tags: bug, orm\n        :tickets: 4334\n        :versions: 1.3.0b1\n\n        Fixed bug where use of :class:`.Lateral` construct in conjunction with\n        :meth:`.Query.join` as well as :meth:`.Query.select_entity_from` would not\n        apply clause adaption to the right side of the join.   &quot;lateral&quot; introduces\n        the use case of the right side of a join being correlatable.  Previously,\n        adaptation of this clause wasn&#39;t considered.   Note that in 1.2 only,\n        a selectable introduced by :meth:`.Query.subquery` is still not adapted\n        due to :ticket:`4304`; the selectable needs to be produced by the\n        :func:`.select` function to be the right side of the &quot;lateral&quot; join.\n\n    .. change::\n       :tags: bug, oracle\n       :tickets: 4335\n\n       Fixed issue for cx_Oracle 7.0 where the behavior of Oracle param.getvalue()\n       now returns a list, rather than a single scalar value, breaking\n       autoincrement logic throughout the Core and ORM. The dml_ret_array_val\n       compatibility flag is used for cx_Oracle 6.3 and 6.4 to establish compatible\n       behavior with 7.0 and forward, for cx_Oracle 6.2.1 and prior a version\n       number check falls back to the old logic.\n\n\n    .. change::\n        :tags: bug, orm\n        :tickets: 4327\n\n        Fixed 1.2 regression caused by :ticket:`3472` where the handling of an\n        &quot;updated_at&quot; style column within the context of a post-update operation\n        would also occur for a row that is to be deleted following the update,\n        meaning both that a column with a Python-side value generator would show\n        the now-deleted value that was emitted for the UPDATE before the DELETE\n        (which was not the previous behavor), as well as that a SQL- emitted value\n        generator would have the attribute expired, meaning the previous value\n        would be unreachable due to the row having been deleted and the object\n        detached from the session.The &quot;postfetch&quot; logic that was added as part of\n        :ticket:`3472` is now skipped entirely for an object that ultimately is to\n        be deleted.\n\n.. changelog::\n   ```\n   \n  \n  \n   ### 1.2.11\n   ```\n   :released: August 20, 2018\n\n    .. change::\n        :tags: bug, py3k\n\n        Started importing &quot;collections&quot; from &quot;collections.abc&quot; under Python 3.3 and\n        greater for Python 3.8 compatibility.  Pull request courtesy Nathaniel\n        Knight.\n\n    .. change::\n        :tag: bug, sqlite\n\n        Fixed issue where the &quot;schema&quot; name used for a SQLite database within table\n        reflection would not quote the schema name correctly.  Pull request\n        courtesy Phillip Cloud.\n\n    .. change::\n        :tags: bug, sql\n        :tickets: 4320\n\n        Fixed issue that is closely related to :ticket:`3639` where an expression\n        rendered in a boolean context on a non-native boolean backend would\n        be compared to 1/0 even though it is already an implcitly boolean\n        expression, when :meth:`.ColumnElement.self_group` were used.  While this\n        does not affect the user-friendly backends (MySQL, SQLite) it was not\n        handled by Oracle (and possibly SQL Server).   Whether or not the\n        expression is implicitly boolean on any database is now determined\n        up front as an additional check to not generate the integer comparison\n        within the compliation of the statement.\n\n    .. change::\n        :tags: bug, oracle\n        :tickets: 4309\n\n        For cx_Oracle, Integer datatypes will now be bound to &quot;int&quot;, per advice\n        from the cx_Oracle developers.  Previously, using cx_Oracle.NUMBER caused a\n        loss in precision within the cx_Oracle 6.x series.\n\n\n    .. change::\n        :tags: bug, orm, declarative\n        :tickets: 4321\n\n        Fixed issue in previously untested use case, allowing a declarative mapped\n        class to inherit from a classically-mapped class outside of the declarative\n        base, including that it accommodates for unmapped intermediate classes. An\n        unmapped intermediate class may specify ``__abstract__``, which is now\n        interpreted correctly, or the intermediate class can remain unmarked, and\n        the classically mapped base class will be detected within the hierarchy\n        regardless. In order to anticipate existing scenarios which may be mixing\n        in classical mappings into existing declarative hierarchies, an error is\n        now raised if multiple mapped bases are detected for a given class.\n\n    .. change::\n        :tags: bug, sql\n        :tickets: 4322\n\n        Added missing window function parameters\n        :paramref:`.WithinGroup.over.range_` and :paramref:`.WithinGroup.over.rows`\n        parameters to the :meth:`.WithinGroup.over` and\n        :meth:`.FunctionFilter.over` methods, to correspond to the range/rows\n        feature added to the &quot;over&quot; method of SQL functions as part of\n        :ticket:`3049` in version 1.1.\n\n    .. change::\n        :tags: bug, sql\n        :tickets: 4313\n\n        Fixed bug where the multi-table support for UPDATE and DELETE statements\n        did not consider the additional FROM elements as targets for correlation,\n        when a correlated SELECT were also combined with the statement.  This\n        change now includes that a SELECT statement in the WHERE clause for such a\n        statement will try to auto-correlate back to these additional tables in the\n        parent UPDATE/DELETE or unconditionally correlate if\n        :meth:`.Select.correlate` is used.  Note that auto-correlation raises an\n        error if the SELECT statement would have no FROM clauses as a result, which\n        can now occur if the parent UPDATE/DELETE specifies the same tables in its\n        additional set of tables; specify :meth:`.Select.correlate` explicitly to\n        resolve.\n\n.. changelog::\n   ```\n   \n  \n  \n   ### 1.2.10\n   ```\n   :released: July 13, 2018\n\n    .. change::\n        :tags: bug, sql\n        :tickets: 4300\n\n        Fixed bug where a :class:`.Sequence` would be dropped explicitly before any\n        :class:`.Table` that refers to it, which breaks in the case when the\n        sequence is also involved in a server-side default for that table, when\n        using :meth:`.MetaData.drop_all`.   The step which processes sequences\n        to be dropped via non server-side column default functions is now invoked\n        after the table itself is dropped.\n\n    .. change::\n        :tags: bug, orm\n        :tickets: 4295\n\n        Fixed bug in :class:`.Bundle` construct where placing two columns of the\n        same name would be de-duplicated, when the :class:`.Bundle` were used as\n        part of the rendered SQL, such as in the ORDER BY or GROUP BY of the statement.\n\n\n    .. change::\n        :tags: bug, orm\n        :tickets: 4298\n\n        Fixed regression in 1.2.9 due to :ticket:`4287` where using a\n        :class:`.Load` option in conjunction with a string wildcard would result\n        in a TypeError.\n\n.. changelog::\n   ```\n   \n  \n</details>\n\n\n \n\n<details>\n  <summary>Links</summary>\n  \n  - PyPI: https://pypi.org/project/sqlalchemy\n  - Changelog: https://pyup.io/changelogs/sqlalchemy/\n  - Homepage: http://www.sqlalchemy.org\n</details>\n\n\n\n\n\n### Update [python-telegram-bot](https://pypi.org/project/python-telegram-bot) from **10.1.0** to **11.1.0**.\n\n\n<details>\n  <summary>Changelog</summary>\n  \n  \n   ### 11.1.0\n   ```\n   Fixes and updates for Telegram Passport: (`1198`_)\n\n- Fix passport decryption failing at random times\n- Added support for middle names.\n- Added support for translations for documents\n- Add errors for translations for documents\n- Added support for requesting names in the language of the user&#39;s country of residence\n- Replaced the payload parameter with the new parameter nonce\n- Add hash to EncryptedPassportElement\n\n.. _`1198`: https://github.com/python-telegram-bot/python-telegram-bot/pull/1198\n\n**2018-08-29**\n   ```\n   \n  \n  \n  \n</details>\n\n\n \n\n<details>\n  <summary>Links</summary>\n  \n  - PyPI: https://pypi.org/project/python-telegram-bot\n  - Changelog: https://pyup.io/changelogs/python-telegram-bot/\n  - Homepage: https://python-telegram-bot.org/\n</details>\n\n\n\n\n\n### Update [pandas](https://pypi.org/project/pandas) from **0.23.3** to **0.23.4**.\n\n\n<details>\n  <summary>Changelog</summary>\n  \n  \n   ### 0.23.4\n   ```\n   ------------------------\n\nThis is a minor bug-fix release in the 0.23.x series and includes some small regression fixes\nand bug fixes. We recommend that all users upgrade to this version.\n\n.. warning::\n\n   Starting January 1, 2019, pandas feature releases will support Python 3 only.\n   See :ref:`install.dropping-27` for more.\n\n.. contents:: What&#39;s new in v0.23.4\n    :local:\n    :backlinks: none\n\n.. _whatsnew_0234.fixed_regressions:\n\nFixed Regressions\n~~~~~~~~~~~~~~~~~\n\n- Python 3.7 with Windows gave all missing values for rolling variance calculations (:issue:`21813`)\n\n.. _whatsnew_0234.bug_fixes:\n\nBug Fixes\n~~~~~~~~~\n\n**Groupby/Resample/Rolling**\n\n- Bug where calling :func:`DataFrameGroupBy.agg` with a list of functions including ``ohlc`` as the non-initial element would raise a ``ValueError`` (:issue:`21716`)\n- Bug in ``roll_quantile`` caused a memory leak when calling ``.rolling(...).quantile(q)`` with ``q`` in (0,1) (:issue:`21965`)\n\n**Missing**\n\n- Bug in :func:`Series.clip` and :func:`DataFrame.clip` cannot accept list-like threshold containing ``NaN`` (:issue:`19992`)\n   ```\n   \n  \n</details>\n\n\n \n\n<details>\n  <summary>Links</summary>\n  \n  - PyPI: https://pypi.org/project/pandas\n  - Changelog: https://pyup.io/changelogs/pandas/\n  - Homepage: http://pandas.pydata.org\n</details>\n\n\n\n\n\n### Update [scikit-learn](https://pypi.org/project/scikit-learn) from **0.19.1** to **0.19.2**.\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/scikit-learn\n  - Changelog: https://pyup.io/changelogs/scikit-learn/\n  - Homepage: http://scikit-learn.org\n</details>\n\n\n\n\n\n### Update [numpy](https://pypi.org/project/numpy) from **1.14.5** to **1.15.2**.\n\n\n<details>\n  <summary>Changelog</summary>\n  \n  \n   ### 1.15.1\n   ```\n   ==========================\n\nThis is a bugfix release for bugs and regressions reported following the 1.15.0\nrelease.\n\n* The annoying but harmless RuntimeWarning that &quot;numpy.dtype size changed&quot; has\n  been suppressed. The long standing suppression was lost in the transition to\n  pytest.\n* The update to Cython 0.28.3 exposed a problematic use of a gcc attribute used\n  to prefer code size over speed in module initialization, possibly resulting in\n  incorrect compiled code. This has been fixed in latest Cython but has been\n  disabled here for safety.\n* Support for big-endian and ARMv8 architectures has been improved.\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\nCompatibility Note\n==================\n\nThe NumPy 1.15.x OS X wheels released on PyPI no longer contain 32-bit\nbinaries.  That will also be the case in future releases. See\n`11625 &lt;https://github.com/numpy/numpy/issues/11625&gt;`__ for the related\ndiscussion.  Those needing 32-bit support should look elsewhere or build\nfrom source.\n\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* Charles Harris\n* Chris Billington\n* Elliott Sales de Andrade +\n* Eric Wieser\n* Jeremy Manning +\n* Matti Picus\n* Ralf Gommers\n\nPull requests merged\n====================\n\nA total of 24 pull requests were merged for this release.\n\n* `11647 &lt;https://github.com/numpy/numpy/pull/11647&gt;`__: MAINT: Filter Cython warnings in ``__init__.py``\n* `11648 &lt;https://github.com/numpy/numpy/pull/11648&gt;`__: BUG: Fix doc source links to unwrap decorators\n* `11657 &lt;https://github.com/numpy/numpy/pull/11657&gt;`__: BUG: Ensure singleton dimensions are not dropped when converting...\n* `11661 &lt;https://github.com/numpy/numpy/pull/11661&gt;`__: BUG: Warn on Nan in minimum,maximum for scalars\n* `11665 &lt;https://github.com/numpy/numpy/pull/11665&gt;`__: BUG: cython sometimes emits invalid gcc attribute\n* `11682 &lt;https://github.com/numpy/numpy/pull/11682&gt;`__: BUG: Fix regression in void_getitem\n* `11698 &lt;https://github.com/numpy/numpy/pull/11698&gt;`__: BUG: Make matrix_power again work for object arrays.\n* `11700 &lt;https://github.com/numpy/numpy/pull/11700&gt;`__: BUG: Add missing PyErr_NoMemory after failing malloc\n* `11719 &lt;https://github.com/numpy/numpy/pull/11719&gt;`__: BUG: Fix undefined functions on big-endian systems.\n* `11720 &lt;https://github.com/numpy/numpy/pull/11720&gt;`__: MAINT: Make einsum optimize default to False.\n* `11746 &lt;https://github.com/numpy/numpy/pull/11746&gt;`__: BUG: Fix regression in loadtxt for bz2 text files in Python 2.\n* `11757 &lt;https://github.com/numpy/numpy/pull/11757&gt;`__: BUG: Revert use of `console_scripts`.\n* `11758 &lt;https://github.com/numpy/numpy/pull/11758&gt;`__: BUG: Fix Fortran kind detection for aarch64 &amp; s390x.\n* `11759 &lt;https://github.com/numpy/numpy/pull/11759&gt;`__: BUG: Fix printing of longdouble on ppc64le.\n* `11760 &lt;https://github.com/numpy/numpy/pull/11760&gt;`__: BUG: Fixes for unicode field names in Python 2\n* `11761 &lt;https://github.com/numpy/numpy/pull/11761&gt;`__: BUG: Increase required cython version on python 3.7\n* `11763 &lt;https://github.com/numpy/numpy/pull/11763&gt;`__: BUG: check return value of _buffer_format_string\n* `11775 &lt;https://github.com/numpy/numpy/pull/11775&gt;`__: MAINT: Make assert_array_compare more generic.\n* `11776 &lt;https://github.com/numpy/numpy/pull/11776&gt;`__: TST: Fix urlopen stubbing.\n* `11777 &lt;https://github.com/numpy/numpy/pull/11777&gt;`__: BUG: Fix regression in intersect1d.\n* `11779 &lt;https://github.com/numpy/numpy/pull/11779&gt;`__: BUG: Fix test sensitive to platform byte order.\n* `11781 &lt;https://github.com/numpy/numpy/pull/11781&gt;`__: BUG: Avoid signed overflow in histogram\n* `11785 &lt;https://github.com/numpy/numpy/pull/11785&gt;`__: BUG: Fix pickle and memoryview for datetime64, timedelta64 scalars\n* `11786 &lt;https://github.com/numpy/numpy/pull/11786&gt;`__: BUG: Deprecation triggers segfault\n\n\n==========================\n   ```\n   \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</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### Update [pytest](https://pypi.org/project/pytest) from **3.6.3** to **3.8.1**.\n\n\n<details>\n  <summary>Changelog</summary>\n  \n  \n   ### 3.8.1\n   ```\n   =========================\n\nBug Fixes\n---------\n\n- `3286 &lt;https://github.com/pytest-dev/pytest/issues/3286&gt;`_: ``.pytest_cache`` directory is now automatically ignored by Git. Users who would like to contribute a solution for other SCMs please consult/comment on this issue.\n\n\n- `3749 &lt;https://github.com/pytest-dev/pytest/issues/3749&gt;`_: Fix the following error during collection of tests inside packages::\n\n      TypeError: object of type &#39;Package&#39; has no len()\n\n\n- `3941 &lt;https://github.com/pytest-dev/pytest/issues/3941&gt;`_: Fix bug where indirect parametrization would consider the scope of all fixtures used by the test function to determine the parametrization scope, and not only the scope of the fixtures being parametrized.\n\n\n- `3973 &lt;https://github.com/pytest-dev/pytest/issues/3973&gt;`_: Fix crash of the assertion rewriter if a test changed the current working directory without restoring it afterwards.\n\n\n- `3998 &lt;https://github.com/pytest-dev/pytest/issues/3998&gt;`_: Fix issue that prevented some caplog properties (for example ``record_tuples``) from being available when entering the debugger with ``--pdb``.\n\n\n- `3999 &lt;https://github.com/pytest-dev/pytest/issues/3999&gt;`_: Fix ``UnicodeDecodeError`` in python2.x when a class returns a non-ascii binary ``__repr__`` in an assertion which also contains non-ascii text.\n\n\n\nImproved Documentation\n----------------------\n\n- `3996 &lt;https://github.com/pytest-dev/pytest/issues/3996&gt;`_: New `Deprecations and Removals &lt;https://docs.pytest.org/en/latest/deprecations.html&gt;`_ page shows all currently\n  deprecated features, the rationale to do so, and alternatives to update your code. It also list features removed\n  from pytest in past major releases to help those with ancient pytest versions to upgrade.\n\n\n\nTrivial/Internal Changes\n------------------------\n\n- `3955 &lt;https://github.com/pytest-dev/pytest/issues/3955&gt;`_: Improve pre-commit detection for changelog filenames\n\n\n- `3975 &lt;https://github.com/pytest-dev/pytest/issues/3975&gt;`_: Remove legacy code around im_func as that was python2 only\n   ```\n   \n  \n  \n   ### 3.8.0\n   ```\n   =========================\n\nDeprecations and Removals\n-------------------------\n\n- `2452 &lt;https://github.com/pytest-dev/pytest/issues/2452&gt;`_: ``Config.warn`` and ``Node.warn`` have been\n  deprecated, see `&lt;https://docs.pytest.org/en/latest/deprecations.htmlconfig-warn-and-node-warn&gt;`_ for rationale and\n  examples.\n\n- `3936 &lt;https://github.com/pytest-dev/pytest/issues/3936&gt;`_: ``pytest.mark.filterwarnings`` second parameter is no longer regex-escaped,\n  making it possible to actually use regular expressions to check the warning message.\n\n  **Note**: regex-escaping the match string was an implementation oversight that might break test suites which depend\n  on the old behavior.\n\n\n\nFeatures\n--------\n\n- `2452 &lt;https://github.com/pytest-dev/pytest/issues/2452&gt;`_: Internal pytest warnings are now issued using the standard ``warnings`` module, making it possible to use\n  the standard warnings filters to manage those warnings. This introduces ``PytestWarning``,\n  ``PytestDeprecationWarning`` and ``RemovedInPytest4Warning`` warning types as part of the public API.\n\n  Consult `the documentation &lt;https://docs.pytest.org/en/latest/warnings.htmlinternal-pytest-warnings&gt;`_ for more info.\n\n\n- `2908 &lt;https://github.com/pytest-dev/pytest/issues/2908&gt;`_: ``DeprecationWarning`` and ``PendingDeprecationWarning`` are now shown by default if no other warning filter is\n  configured. This makes pytest more compliant with\n  `PEP-0506 &lt;https://www.python.org/dev/peps/pep-0565/recommended-filter-settings-for-test-runners&gt;`_. See\n  `the docs &lt;https://docs.pytest.org/en/latest/warnings.htmldeprecationwarning-and-pendingdeprecationwarning&gt;`_ for\n  more info.\n\n\n- `3251 &lt;https://github.com/pytest-dev/pytest/issues/3251&gt;`_: Warnings are now captured and displayed during test collection.\n\n\n- `3784 &lt;https://github.com/pytest-dev/pytest/issues/3784&gt;`_: ``PYTEST_DISABLE_PLUGIN_AUTOLOAD`` environment variable disables plugin auto-loading when set.\n\n\n- `3829 &lt;https://github.com/pytest-dev/pytest/issues/3829&gt;`_: Added the ``count`` option to ``console_output_style`` to enable displaying the progress as a count instead of a percentage.\n\n\n- `3837 &lt;https://github.com/pytest-dev/pytest/issues/3837&gt;`_: Added support for &#39;xfailed&#39; and &#39;xpassed&#39; outcomes to the ``pytester.RunResult.assert_outcomes`` signature.\n\n\n\nBug Fixes\n---------\n\n- `3911 &lt;https://github.com/pytest-dev/pytest/issues/3911&gt;`_: Terminal writer now takes into account unicode character width when writing out progress.\n\n\n- `3913 &lt;https://github.com/pytest-dev/pytest/issues/3913&gt;`_: Pytest now returns with correct exit code (EXIT_USAGEERROR, 4) when called with unknown arguments.\n\n\n- `3918 &lt;https://github.com/pytest-dev/pytest/issues/3918&gt;`_: Improve performance of assertion rewriting.\n\n\n\nImproved Documentation\n----------------------\n\n- `3566 &lt;https://github.com/pytest-dev/pytest/issues/3566&gt;`_: Added a blurb in usage.rst for the usage of -r flag which is used to show an extra test summary info.\n\n\n- `3907 &lt;https://github.com/pytest-dev/pytest/issues/3907&gt;`_: Corrected type of the exceptions collection passed to ``xfail``: ``raises`` argument accepts a ``tuple`` instead of ``list``.\n\n\n\nTrivial/Internal Changes\n------------------------\n\n- `3853 &lt;https://github.com/pytest-dev/pytest/issues/3853&gt;`_: Removed ``&quot;run all (no recorded failures)&quot;`` message printed with ``--failed-first`` and ``--last-failed`` when there are no failed tests.\n   ```\n   \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 &lt;https://docs.pytest.org/en/latest/deprecations.htmlpytest-namespace&gt;`_.\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``. See `the documentation for rationale and examples &lt;https://docs.pytest.org/en/latest/deprecations.htmlcalling-fixtures-directly&gt;`_.\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</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-cov](https://pypi.org/project/pytest-cov) from **2.5.1** to **2.6.0**.\n\n\n<details>\n  <summary>Changelog</summary>\n  \n  \n   ### 2.6.0\n   ```\n   ------------------\n\n* Dropped support for Python &lt; 3.4, Pytest &lt; 3.5 and Coverage &lt; 4.4.\n* Fixed some documentation formatting. Contributed by Jean Jordaan and Julian.\n* Added an example with ``addopts`` in documentation. Contributed by Samuel Giffard in\n  `195 &lt;https://github.com/pytest-dev/pytest-cov/pull/195&gt;`_.\n* Fixed ``TypeError: &#39;NoneType&#39; object is not iterable`` in certain xdist configurations. Contributed by Jeremy Bowman in\n  `213 &lt;https://github.com/pytest-dev/pytest-cov/pull/213&gt;`_.\n* Added a ``no_cover`` marker and fixture. Fixes\n  `78 &lt;https://github.com/pytest-dev/pytest-cov/issues/78&gt;`_.\n* Fixed broken ``no_cover`` check when running doctests. Contributed by Terence Honles in\n  `200 &lt;https://github.com/pytest-dev/pytest-cov/pull/200&gt;`_.\n* Fixed various issues with path normalization in reports (when combining coverage data from parallel mode). Fixes\n  `130 &lt;https://github.com/pytest-dev/pytest-cov/issues/161&gt;`_.\n  Contributed by Ryan Hiebert &amp; Ionel Cristian Mărieș in\n  `178 &lt;https://github.com/pytest-dev/pytest-cov/pull/178&gt;`_.\n* Report generation failures don&#39;t raise exceptions anymore. A warning will be logged instead. Fixes\n  `161 &lt;https://github.com/pytest-dev/pytest-cov/issues/161&gt;`_.\n* Fixed multiprocessing issue on Windows (empty env vars are not passed). Fixes\n  `165 &lt;https://github.com/pytest-dev/pytest-cov/issues/165&gt;`_.\n   ```\n   \n  \n</details>\n\n\n \n\n<details>\n  <summary>Links</summary>\n  \n  - PyPI: https://pypi.org/project/pytest-cov\n  - Changelog: https://pyup.io/changelogs/pytest-cov/\n  - Repo: https://github.com/pytest-dev/pytest-cov\n</details>\n\n\n\n\n\n### Update [hyperopt](https://pypi.org/project/hyperopt) from **0.1** to **0.1.1**.\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/hyperopt\n  - Changelog: https://pyup.io/changelogs/hyperopt/\n  - Repo: http://hyperopt.github.com/hyperopt/\n</details>\n\n\n\n\n\n### Update [networkx](https://pypi.org/project/networkx) from **1.11** to **2.2**.\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/networkx\n  - Repo: http://networkx.github.io/\n</details>\n\n\n\n\n\n### Update [simplejson](https://pypi.org/project/simplejson) from **3.16.0** to **3.16.1**.\n\n\n<details>\n  <summary>Changelog</summary>\n  \n  \n   ### 3.16.1\n   ```\n   * Added examples for JSON lines use cases\n  https://github.com/simplejson/simplejson/pull/236\n* Add wheels for more Python versions and platforms\n  https://github.com/simplejson/simplejson/pull/234\n  https://github.com/simplejson/simplejson/pull/233\n  https://github.com/simplejson/simplejson/pull/231\n   ```\n   \n  \n</details>\n\n\n \n\n<details>\n  <summary>Links</summary>\n  \n  - PyPI: https://pypi.org/project/simplejson\n  - Changelog: https://pyup.io/changelogs/simplejson/\n  - Repo: https://github.com/simplejson/simplejson\n</details>\n\n\n\n\n\n","created_at":"2018-09-23T12:58:23Z","updated_at":"2018-09-24T12:58:29Z","closed_at":"2018-09-24T12:58:29Z","merged_at":null,"merge_commit_sha":"530438804a4cf60949391cc310e51b78daba1549","assignee":null,"assignees":[],"requested_reviewers":[],"requested_teams":[],"labels":[],"milestone":null,"commits_url":"https://api.github.com/repos/nullart/freqtrade/pulls/82/commits","review_comments_url":"https://api.github.com/repos/nullart/freqtrade/pulls/82/comments","review_comment_url":"https://api.github.com/repos/nullart/freqtrade/pulls/comments{/number}","comments_url":"https://api.github.com/repos/nullart/freqtrade/issues/82/comments","statuses_url":"https://api.github.com/repos/nullart/freqtrade/statuses/93bdf5501fa7214bc7f94e95b8dbfe56926c5522","head":{"label":"nullart:pyup-scheduled-update-2018-09-23","ref":"pyup-scheduled-update-2018-09-23","sha":"93bdf5501fa7214bc7f94e95b8dbfe56926c5522","user":{"login":"nullart","id":448013,"node_id":"MDQ6VXNlcjQ0ODAxMw==","avatar_url":"https://avatars1.githubusercontent.com/u/448013?v=4","gravatar_id":"","url":"https://api.github.com/users/nullart","html_url":"https://github.com/nullart","followers_url":"https://api.github.com/users/nullart/followers","following_url":"https://api.github.com/users/nullart/following{/other_user}","gists_url":"https://api.github.com/users/nullart/gists{/gist_id}","starred_url":"https://api.github.com/users/nullart/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/nullart/subscriptions","organizations_url":"https://api.github.com/users/nullart/orgs","repos_url":"https://api.github.com/users/nullart/repos","events_url":"https://api.github.com/users/nullart/events{/privacy}","received_events_url":"https://api.github.com/users/nullart/received_events","type":"User","site_admin":false},"repo":{"id":132007590,"node_id":"MDEwOlJlcG9zaXRvcnkxMzIwMDc1OTA=","name":"freqtrade","full_name":"nullart/freqtrade","private":false,"owner":{"login":"nullart","id":448013,"node_id":"MDQ6VXNlcjQ0ODAxMw==","avatar_url":"https://avatars1.githubusercontent.com/u/448013?v=4","gravatar_id":"","url":"https://api.github.com/users/nullart","html_url":"https://github.com/nullart","followers_url":"https://api.github.com/users/nullart/followers","following_url":"https://api.github.com/users/nullart/following{/other_user}","gists_url":"https://api.github.com/users/nullart/gists{/gist_id}","starred_url":"https://api.github.com/users/nullart/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/nullart/subscriptions","organizations_url":"https://api.github.com/users/nullart/orgs","repos_url":"https://api.github.com/users/nullart/repos","events_url":"https://api.github.com/users/nullart/events{/privacy}","received_events_url":"https://api.github.com/users/nullart/received_events","type":"User","site_admin":false},"html_url":"https://github.com/nullart/freqtrade","description":"Simple High Frequency Trading Bot for crypto currencies","fork":true,"url":"https://api.github.com/repos/nullart/freqtrade","forks_url":"https://api.github.com/repos/nullart/freqtrade/forks","keys_url":"https://api.github.com/repos/nullart/freqtrade/keys{/key_id}","collaborators_url":"https://api.github.com/repos/nullart/freqtrade/collaborators{/collaborator}","teams_url":"https://api.github.com/repos/nullart/freqtrade/teams","hooks_url":"https://api.github.com/repos/nullart/freqtrade/hooks","issue_events_url":"https://api.github.com/repos/nullart/freqtrade/issues/events{/number}","events_url":"https://api.github.com/repos/nullart/freqtrade/events","assignees_url":"https://api.github.com/repos/nullart/freqtrade/assignees{/user}","branches_url":"https://api.github.com/repos/nullart/freqtrade/branches{/branch}","tags_url":"https://api.github.com/repos/nullart/freqtrade/tags","blobs_url":"https://api.github.com/repos/nullart/freqtrade/git/blobs{/sha}","git_tags_url":"https://api.github.com/repos/nullart/freqtrade/git/tags{/sha}","git_refs_url":"https://api.github.com/repos/nullart/freqtrade/git/refs{/sha}","trees_url":"https://api.github.com/repos/nullart/freqtrade/git/trees{/sha}","statuses_url":"https://api.github.com/repos/nullart/freqtrade/statuses/{sha}","languages_url":"https://api.github.com/repos/nullart/freqtrade/languages","stargazers_url":"https://api.github.com/repos/nullart/freqtrade/stargazers","contributors_url":"https://api.github.com/repos/nullart/freqtrade/contributors","subscribers_url":"https://api.github.com/repos/nullart/freqtrade/subscribers","subscription_url":"https://api.github.com/repos/nullart/freqtrade/subscription","commits_url":"https://api.github.com/repos/nullart/freqtrade/commits{/sha}","git_commits_url":"https://api.github.com/repos/nullart/freqtrade/git/commits{/sha}","comments_url":"https://api.github.com/repos/nullart/freqtrade/comments{/number}","issue_comment_url":"https://api.github.com/repos/nullart/freqtrade/issues/comments{/number}","contents_url":"https://api.github.com/repos/nullart/freqtrade/contents/{+path}","compare_url":"https://api.github.com/repos/nullart/freqtrade/compare/{base}...{head}","merges_url":"https://api.github.com/repos/nullart/freqtrade/merges","archive_url":"https://api.github.com/repos/nullart/freqtrade/{archive_format}{/ref}","downloads_url":"https://api.github.com/repos/nullart/freqtrade/downloads","issues_url":"https://api.github.com/repos/nullart/freqtrade/issues{/number}","pulls_url":"https://api.github.com/repos/nullart/freqtrade/pulls{/number}","milestones_url":"https://api.github.com/repos/nullart/freqtrade/milestones{/number}","notifications_url":"https://api.github.com/repos/nullart/freqtrade/notifications{?since,all,participating}","labels_url":"https://api.github.com/repos/nullart/freqtrade/labels{/name}","releases_url":"https://api.github.com/repos/nullart/freqtrade/releases{/id}","deployments_url":"https://api.github.com/repos/nullart/freqtrade/deployments","created_at":"2018-05-03T14:31:51Z","updated_at":"2018-08-26T01:57:46Z","pushed_at":"2018-09-24T12:58:25Z","git_url":"git://github.com/nullart/freqtrade.git","ssh_url":"git@github.com:nullart/freqtrade.git","clone_url":"https://github.com/nullart/freqtrade.git","svn_url":"https://github.com/nullart/freqtrade","homepage":"","size":56859,"stargazers_count":4,"watchers_count":4,"language":"Python","has_issues":true,"has_projects":true,"has_downloads":true,"has_wiki":true,"has_pages":false,"forks_count":1,"mirror_url":null,"archived":false,"open_issues_count":1,"license":{"key":"gpl-3.0","name":"GNU General Public License v3.0","spdx_id":"GPL-3.0","url":"https://api.github.com/licenses/gpl-3.0","node_id":"MDc6TGljZW5zZTk="},"forks":1,"open_issues":1,"watchers":4,"default_branch":"develop"}},"base":{"label":"nullart:develop","ref":"develop","sha":"6e9e8789a539374ba9e1f12d9f58574f112fbb67","user":{"login":"nullart","id":448013,"node_id":"MDQ6VXNlcjQ0ODAxMw==","avatar_url":"https://avatars1.githubusercontent.com/u/448013?v=4","gravatar_id":"","url":"https://api.github.com/users/nullart","html_url":"https://github.com/nullart","followers_url":"https://api.github.com/users/nullart/followers","following_url":"https://api.github.com/users/nullart/following{/other_user}","gists_url":"https://api.github.com/users/nullart/gists{/gist_id}","starred_url":"https://api.github.com/users/nullart/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/nullart/subscriptions","organizations_url":"https://api.github.com/users/nullart/orgs","repos_url":"https://api.github.com/users/nullart/repos","events_url":"https://api.github.com/users/nullart/events{/privacy}","received_events_url":"https://api.github.com/users/nullart/received_events","type":"User","site_admin":false},"repo":{"id":132007590,"node_id":"MDEwOlJlcG9zaXRvcnkxMzIwMDc1OTA=","name":"freqtrade","full_name":"nullart/freqtrade","private":false,"owner":{"login":"nullart","id":448013,"node_id":"MDQ6VXNlcjQ0ODAxMw==","avatar_url":"https://avatars1.githubusercontent.com/u/448013?v=4","gravatar_id":"","url":"https://api.github.com/users/nullart","html_url":"https://github.com/nullart","followers_url":"https://api.github.com/users/nullart/followers","following_url":"https://api.github.com/users/nullart/following{/other_user}","gists_url":"https://api.github.com/users/nullart/gists{/gist_id}","starred_url":"https://api.github.com/users/nullart/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/nullart/subscriptions","organizations_url":"https://api.github.com/users/nullart/orgs","repos_url":"https://api.github.com/users/nullart/repos","events_url":"https://api.github.com/users/nullart/events{/privacy}","received_events_url":"https://api.github.com/users/nullart/received_events","type":"User","site_admin":false},"html_url":"https://github.com/nullart/freqtrade","description":"Simple High Frequency Trading Bot for crypto currencies","fork":true,"url":"https://api.github.com/repos/nullart/freqtrade","forks_url":"https://api.github.com/repos/nullart/freqtrade/forks","keys_url":"https://api.github.com/repos/nullart/freqtrade/keys{/key_id}","collaborators_url":"https://api.github.com/repos/nullart/freqtrade/collaborators{/collaborator}","teams_url":"https://api.github.com/repos/nullart/freqtrade/teams","hooks_url":"https://api.github.com/repos/nullart/freqtrade/hooks","issue_events_url":"https://api.github.com/repos/nullart/freqtrade/issues/events{/number}","events_url":"https://api.github.com/repos/nullart/freqtrade/events","assignees_url":"https://api.github.com/repos/nullart/freqtrade/assignees{/user}","branches_url":"https://api.github.com/repos/nullart/freqtrade/branches{/branch}","tags_url":"https://api.github.com/repos/nullart/freqtrade/tags","blobs_url":"https://api.github.com/repos/nullart/freqtrade/git/blobs{/sha}","git_tags_url":"https://api.github.com/repos/nullart/freqtrade/git/tags{/sha}","git_refs_url":"https://api.github.com/repos/nullart/freqtrade/git/refs{/sha}","trees_url":"https://api.github.com/repos/nullart/freqtrade/git/trees{/sha}","statuses_url":"https://api.github.com/repos/nullart/freqtrade/statuses/{sha}","languages_url":"https://api.github.com/repos/nullart/freqtrade/languages","stargazers_url":"https://api.github.com/repos/nullart/freqtrade/stargazers","contributors_url":"https://api.github.com/repos/nullart/freqtrade/contributors","subscribers_url":"https://api.github.com/repos/nullart/freqtrade/subscribers","subscription_url":"https://api.github.com/repos/nullart/freqtrade/subscription","commits_url":"https://api.github.com/repos/nullart/freqtrade/commits{/sha}","git_commits_url":"https://api.github.com/repos/nullart/freqtrade/git/commits{/sha}","comments_url":"https://api.github.com/repos/nullart/freqtrade/comments{/number}","issue_comment_url":"https://api.github.com/repos/nullart/freqtrade/issues/comments{/number}","contents_url":"https://api.github.com/repos/nullart/freqtrade/contents/{+path}","compare_url":"https://api.github.com/repos/nullart/freqtrade/compare/{base}...{head}","merges_url":"https://api.github.com/repos/nullart/freqtrade/merges","archive_url":"https://api.github.com/repos/nullart/freqtrade/{archive_format}{/ref}","downloads_url":"https://api.github.com/repos/nullart/freqtrade/downloads","issues_url":"https://api.github.com/repos/nullart/freqtrade/issues{/number}","pulls_url":"https://api.github.com/repos/nullart/freqtrade/pulls{/number}","milestones_url":"https://api.github.com/repos/nullart/freqtrade/milestones{/number}","notifications_url":"https://api.github.com/repos/nullart/freqtrade/notifications{?since,all,participating}","labels_url":"https://api.github.com/repos/nullart/freqtrade/labels{/name}","releases_url":"https://api.github.com/repos/nullart/freqtrade/releases{/id}","deployments_url":"https://api.github.com/repos/nullart/freqtrade/deployments","created_at":"2018-05-03T14:31:51Z","updated_at":"2018-08-26T01:57:46Z","pushed_at":"2018-09-24T12:58:25Z","git_url":"git://github.com/nullart/freqtrade.git","ssh_url":"git@github.com:nullart/freqtrade.git","clone_url":"https://github.com/nullart/freqtrade.git","svn_url":"https://github.com/nullart/freqtrade","homepage":"","size":56859,"stargazers_count":4,"watchers_count":4,"language":"Python","has_issues":true,"has_projects":true,"has_downloads":true,"has_wiki":true,"has_pages":false,"forks_count":1,"mirror_url":null,"archived":false,"open_issues_count":1,"license":{"key":"gpl-3.0","name":"GNU General Public License v3.0","spdx_id":"GPL-3.0","url":"https://api.github.com/licenses/gpl-3.0","node_id":"MDc6TGljZW5zZTk="},"forks":1,"open_issues":1,"watchers":4,"default_branch":"develop"}},"_links":{"self":{"href":"https://api.github.com/repos/nullart/freqtrade/pulls/82"},"html":{"href":"https://github.com/nullart/freqtrade/pull/82"},"issue":{"href":"https://api.github.com/repos/nullart/freqtrade/issues/82"},"comments":{"href":"https://api.github.com/repos/nullart/freqtrade/issues/82/comments"},"review_comments":{"href":"https://api.github.com/repos/nullart/freqtrade/pulls/82/comments"},"review_comment":{"href":"https://api.github.com/repos/nullart/freqtrade/pulls/comments{/number}"},"commits":{"href":"https://api.github.com/repos/nullart/freqtrade/pulls/82/commits"},"statuses":{"href":"https://api.github.com/repos/nullart/freqtrade/statuses/93bdf5501fa7214bc7f94e95b8dbfe56926c5522"}},"author_association":"NONE","merged":false,"mergeable":true,"rebaseable":true,"mergeable_state":"unstable","merged_by":null,"comments":1,"review_comments":0,"maintainer_can_modify":false,"commits":11,"additions":11,"deletions":11,"changed_files":1}}
{"actor":{"display_login":"pyup-bot"}}