search

jason-neal / companion_simulations

Simulating combined host+companion spectra, and fitting to observed crires spectra.
MIT License
2 stars 0 forks source link

Scheduled biweekly dependency update for week 13 #45

Closed pyup-bot closed 6 years ago

pyup-bot commented 6 years ago

Update scipy from 1.0.0 to 1.0.1.

The bot wasn't able to find a changelog for this release. Got an idea?

Links - PyPI: https://pypi.org/project/scipy - Changelog: https://pyup.io/changelogs/scipy/ - Repo: https://github.com/scipy/scipy/releases - Homepage: https://www.scipy.org

Update sqlalchemy from 1.2.5 to 1.2.6.

Changelog ### 1.2.6 ``` :released: March 30, 2018 .. change:: :tags: bug, mssql :tickets: 4227 :versions: 1.3.0b1 Adjusted the SQL Server version detection for pyodbc to only allow for numeric tokens, filtering out non-integers, since the dialect does tuple- numeric comparisons with this value. This is normally true for all known SQL Server / pyodbc drivers in any case. .. change:: :tags: feature, postgresql :versions: 1.3.0b1 Added support for "PARTITION BY" in Postgresql table definitions, using "postgresql_partition_by". Pull request courtesy Vsevolod Solovyov. .. change:: :tags: bug, sql :tickets: 4204 :versions: 1.3.0b1 Fixed a regression that occurred from the previous fix to :ticket:`4204` in version 1.2.5, where a CTE that refers to itself after the :meth:`.CTE.alias` method has been called would not refer to iself correctly. .. change:: :tags: bug, engine :tickets: 4225 :versions: 1.3.0b1 Fixed bug in connection pool where a connection could be present in the pool without all of its "connect" event handlers called, if a previous "connect" handler threw an exception; note that the dialects themselves have connect handlers that emit SQL, such as those which set transaction isolation, which can fail if the database is in a non-available state, but still allows a connection. The connection is now invalidated first if any of the connect handlers fail. .. change:: :tags: bug, oracle :tickets: 4211 :versions: 1.3.0b1 The minimum cx_Oracle version supported is 5.2 (June 2015). Previously, the dialect asserted against version 5.0 but as of 1.2.2 we are using some symbols that did not appear until 5.2. .. change:: :tags: bug, declarative :tickets: 4221 Removed a warning that would be emitted when calling upon ``__table_args__``, ``__mapper_args__`` as named with a ``declared_attr`` method, when called from a non-mapped declarative mixin. Calling these directly is documented as the approach to use when one is overidding one of these methods on a mapped class. The warning still emits for regular attribute names. .. change:: :tags: bug, orm :tickets: 4215 :versions: 1.3.0b1 Fixed bug where using :meth:`.Mutable.associate_with` or :meth:`.Mutable.as_mutable` in conjunction with a class that has non- primary mappers set up with alternatively-named attributes would produce an attribute error. Since non-primary mappers are not used for persistence, the mutable extension now excludes non-primary mappers from its instrumentation steps. .. changelog:: ```
Links - PyPI: https://pypi.org/project/sqlalchemy - Changelog: https://pyup.io/changelogs/sqlalchemy/ - Homepage: http://www.sqlalchemy.org

Update tqdm from 4.19.8 to 4.20.0.

Changelog ### 4.20.0 ``` - `pandas` wrapper: remove `*args` and add better `total` handling (244, 299, 322, 366 -> 524) - document windows unicode know issues (454) - suppress `RuntimeError: Set changed size during iteration` -> `TqdmSynchronisationWarning` (481) ``` ### 4.19.9 ``` - fix monitor thread termination and update tests (527) ```
Links - PyPI: https://pypi.org/project/tqdm - Changelog: https://pyup.io/changelogs/tqdm/ - Repo: https://github.com/tqdm/tqdm/issues

Update codacy-coverage from 1.3.10 to 1.3.11.

The bot wasn't able to find a changelog for this release. Got an idea?

Links - PyPI: https://pypi.org/project/codacy-coverage - Changelog: https://pyup.io/changelogs/codacy-coverage/ - Repo: https://github.com/codacy/python-codacy-coverage

Update hypothesis from 3.50.2 to 3.53.0.

Changelog ### 3.53.0 ``` ------------------- This release removes support for Django 1.8, which reached end of life on 2018-04-01. `You can see Django's release and support schedule `on the Django Project website <https://www.djangoproject.com/download/supported-versions>`_. ------------------- ``` ### 3.52.3 ``` ------------------- This patch fixes the :obj:`~hypothesis.settings.min_satisfying_examples` settings documentation, by explaining that example shrinking is tracked at the level of the underlying bytestream rather than the output value. The output from :func:`~hypothesis.find` in verbose mode has also been adjusted - see :ref:`the example session <verbose-output>` - to avoid duplicating lines when the example repr is constant, even if the underlying representation has been shrunken. ------------------- ``` ### 3.52.2 ``` ------------------- This release improves the output of failures with :ref:`rule based stateful testing <rulebasedstateful>` in two ways: * The output from it is now usually valid Python code. * When the same value has two different names because it belongs to two different bundles, it will now display with the name associated with the correct bundle for a rule argument where it is used. ------------------- ``` ### 3.52.1 ``` ------------------- This release improves the behaviour of :doc:`stateful testing <stateful>` in two ways: * Previously some runs would run no steps (:issue:`376`). This should no longer happen. * RuleBasedStateMachine tests which used bundles extensively would often shrink terribly. This should now be significantly improved, though there is likely a lot more room for improvement. This release also involves a low level change to how ranges of integers are handles which may result in other improvements to shrink quality in some cases. ------------------- ``` ### 3.52.0 ``` ------------------- This release deprecates use of :func:`settings(...) <hypothesis.settings>` as a decorator, on functions or methods that are not also decorated with :func:`given <hypothesis.given>`. You can still apply these decorators in any order, though you should only do so once each. Applying :func:`given <hypothesis.given>` twice was already deprecated, and applying :func:`settings(...) <hypothesis.settings>` twice is deprecated in this release and will become an error in a future version. Neither could ever be used twice to good effect.) Using :func:`settings(...) <hypothesis.settings>` as the sole decorator on a test is completely pointless, so this common usage error will become an error in a future version of Hypothesis. ------------------- ``` ### 3.51.0 ``` ------------------- This release deprecates the ``average_size`` argument to :func:`~hypothesis.strategies.lists` and other collection strategies. You should simply delete it wherever it was used in your tests, as it no longer has any effect. In early versions of Hypothesis, the ``average_size`` argument was treated as a hint about the distribution of examples from a strategy. Subsequent improvements to the conceptual model and the engine for generating and shrinking examples mean it is more effective to simply describe what constitutes a valid example, and let our internals handle the distribution. ------------------- ``` ### 3.50.3 ``` ------------------- This patch contains some internal refactoring so that we can run with warnings as errors in CI. ------------------- ```
Links - PyPI: https://pypi.org/project/hypothesis - Changelog: https://pyup.io/changelogs/hypothesis/ - Repo: https://github.com/HypothesisWorks/hypothesis/issues

Update pytest from 3.4.2 to 3.5.0.

Changelog ### 3.5.0 ``` ========================= Deprecations and Removals ------------------------- - ``record_xml_property`` fixture is now deprecated in favor of the more generic ``record_property``. (`2770 <https://github.com/pytest-dev/pytest/issues/2770>`_) - Defining ``pytest_plugins`` is now deprecated in non-top-level conftest.py files, because they "leak" to the entire directory tree. (`3084 <https://github.com/pytest-dev/pytest/issues/3084>`_) Features -------- - New ``--show-capture`` command-line option that allows to specify how to display captured output when tests fail: ``no``, ``stdout``, ``stderr``, ``log`` or ``all`` (the default). (`1478 <https://github.com/pytest-dev/pytest/issues/1478>`_) - New ``--rootdir`` command-line option to override the rules for discovering the root directory. See `customize <https://docs.pytest.org/en/latest/customize.html>`_ in the documentation for details. (`1642 <https://github.com/pytest-dev/pytest/issues/1642>`_) - Fixtures are now instantiated based on their scopes, with higher-scoped fixtures (such as ``session``) being instantiated first than lower-scoped fixtures (such as ``function``). The relative order of fixtures of the same scope is kept unchanged, based in their declaration order and their dependencies. (`2405 <https://github.com/pytest-dev/pytest/issues/2405>`_) - ``record_xml_property`` renamed to ``record_property`` and is now compatible with xdist, markers and any reporter. ``record_xml_property`` name is now deprecated. (`2770 <https://github.com/pytest-dev/pytest/issues/2770>`_) - New ``--nf``, ``--new-first`` options: run new tests first followed by the rest of the tests, in both cases tests are also sorted by the file modified time, with more recent files coming first. (`3034 <https://github.com/pytest-dev/pytest/issues/3034>`_) - New ``--last-failed-no-failures`` command-line option that allows to specify the behavior of the cache plugin's --last-failed`` feature when no tests failed in the last run (or no cache was found): ``none`` or ``all`` (the default). (`3139 <https://github.com/pytest-dev/pytest/issues/3139>`_) - New ``--doctest-continue-on-failure`` command-line option to enable doctests to show multiple failures for each snippet, instead of stopping at the first failure. (`3149 <https://github.com/pytest-dev/pytest/issues/3149>`_) - Captured log messages are added to the ``<system-out>`` tag in the generated junit xml file if the ``junit_logging`` ini option is set to ``system-out``. If the value of this ini option is ``system-err`, the logs are written to ``<system-err>``. The default value for ``junit_logging`` is ``no``, meaning captured logs are not written to the output file. (`3156 <https://github.com/pytest-dev/pytest/issues/3156>`_) - Allow the logging plugin to handle ``pytest_runtest_logstart`` and ``pytest_runtest_logfinish`` hooks when live logs are enabled. (`3189 <https://github.com/pytest-dev/pytest/issues/3189>`_) - Passing `--log-cli-level` in the command-line now automatically activates live logging. (`3190 <https://github.com/pytest-dev/pytest/issues/3190>`_) - Add command line option ``--deselect`` to allow deselection of individual tests at collection time. (`3198 <https://github.com/pytest-dev/pytest/issues/3198>`_) - Captured logs are printed before entering pdb. (`3204 <https://github.com/pytest-dev/pytest/issues/3204>`_) - Deselected item count is now shown before tests are run, e.g. ``collected X items / Y deselected``. (`3213 <https://github.com/pytest-dev/pytest/issues/3213>`_) - The builtin module ``platform`` is now available for use in expressions in ``pytest.mark``. (`3236 <https://github.com/pytest-dev/pytest/issues/3236>`_) - The *short test summary info* section now is displayed after tracebacks and warnings in the terminal. (`3255 <https://github.com/pytest-dev/pytest/issues/3255>`_) - New ``--verbosity`` flag to set verbosity level explicitly. (`3296 <https://github.com/pytest-dev/pytest/issues/3296>`_) - ``pytest.approx`` now accepts comparing a numpy array with a scalar. (`3312 <https://github.com/pytest-dev/pytest/issues/3312>`_) Bug Fixes --------- - Suppress ``IOError`` when closing the temporary file used for capturing streams in Python 2.7. (`2370 <https://github.com/pytest-dev/pytest/issues/2370>`_) - Fixed ``clear()`` method on ``caplog`` fixture which cleared ``records``, but not the ``text`` property. (`3297 <https://github.com/pytest-dev/pytest/issues/3297>`_) - During test collection, when stdin is not allowed to be read, the ``DontReadFromStdin`` object still allow itself to be iterable and resolved to an iterator without crashing. (`3314 <https://github.com/pytest-dev/pytest/issues/3314>`_) Improved Documentation ---------------------- - Added a `reference <https://docs.pytest.org/en/latest/reference.html>`_ page to the docs. (`1713 <https://github.com/pytest-dev/pytest/issues/1713>`_) Trivial/Internal Changes ------------------------ - Change minimum requirement of ``attrs`` to ``17.4.0``. (`3228 <https://github.com/pytest-dev/pytest/issues/3228>`_) - Renamed example directories so all tests pass when ran from the base directory. (`3245 <https://github.com/pytest-dev/pytest/issues/3245>`_) - Internal ``mark.py`` module has been turned into a package. (`3250 <https://github.com/pytest-dev/pytest/issues/3250>`_) - ``pytest`` now depends on the `more_itertools <https://github.com/erikrose/more-itertools>`_ package. (`3265 <https://github.com/pytest-dev/pytest/issues/3265>`_) - Added warning when ``[pytest]`` section is used in a ``.cfg`` file passed with ``-c`` (`3268 <https://github.com/pytest-dev/pytest/issues/3268>`_) - ``nodeids`` can now be passed explicitly to ``FSCollector`` and ``Node`` constructors. (`3291 <https://github.com/pytest-dev/pytest/issues/3291>`_) - Internal refactoring of ``FormattedExcinfo`` to use ``attrs`` facilities and remove old support code for legacy Python versions. (`3292 <https://github.com/pytest-dev/pytest/issues/3292>`_) - Refactoring to unify how verbosity is handled internally. (`3296 <https://github.com/pytest-dev/pytest/issues/3296>`_) - Internal refactoring to better integrate with argparse. (`3304 <https://github.com/pytest-dev/pytest/issues/3304>`_) - Fix a python example when calling a fixture in doc/en/usage.rst (`3308 <https://github.com/pytest-dev/pytest/issues/3308>`_) ```
Links - PyPI: https://pypi.org/project/pytest - Changelog: https://pyup.io/changelogs/pytest/ - Repo: https://github.com/pytest-dev/pytest/issues - Homepage: http://pytest.org
pyup-bot commented 6 years ago

Closing this in favor of #46