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 11 #44

Closed pyup-bot closed 6 years ago

pyup-bot commented 6 years ago

Update astropy from 3.0 to 3.0.1.

Changelog ### 3.0.1 ``` ================== Bug Fixes --------- astropy.config ^^^^^^^^^^^^^^ astropy.constants ^^^^^^^^^^^^^^^^^ astropy.convolution ^^^^^^^^^^^^^^^^^^^ astropy.coordinates ^^^^^^^^^^^^^^^^^^^ astropy.cosmology ^^^^^^^^^^^^^^^^^ astropy.extern ^^^^^^^^^^^^^^ astropy.io.ascii ^^^^^^^^^^^^^^^^ - Fix a unicode decode error when reading a table with non-ASCII characters. The fast C reader cannot handle unicode so the code now uses the pure-Python reader in this case. [7103] astropy.io.fits ^^^^^^^^^^^^^^^ - Updated the bundled CFITSIO library to 3.430. This is to remedy a critical security vulnerability that was identified by NASA. See ``cextern/cfitsio/docs/changes.txt`` for additional information. [7274] astropy.io.misc ^^^^^^^^^^^^^^^ - Make sure that a sufficiently recent version of ASDF is installed when running test suite against ASDF tags and schemas. [7205] astropy.io.registry ^^^^^^^^^^^^^^^^^^^ - Fix reading files with serialized metadata when using a Table subclass. [7213] astropy.io.votable ^^^^^^^^^^^^^^^^^^ - Fix lookup fields by ID. [7208] astropy.modeling ^^^^^^^^^^^^^^^^ - Fix model set evaluation over common input when model_set_axis > 0. [7222] astropy.nddata ^^^^^^^^^^^^^^ astropy.samp ^^^^^^^^^^^^ astropy.stats ^^^^^^^^^^^^^ astropy.table ^^^^^^^^^^^^^ astropy.tests ^^^^^^^^^^^^^ astropy.time ^^^^^^^^^^^^ astropy.units ^^^^^^^^^^^^^ - ``quantity_helper`` no longer requires ``scipy>=0.18``. [7219] astropy.utils ^^^^^^^^^^^^^ astropy.visualization ^^^^^^^^^^^^^^^^^^^^^ astropy.wcs ^^^^^^^^^^^ ```
Links - PyPI: https://pypi.python.org/pypi/astropy - Changelog: https://pyup.io/changelogs/astropy/ - Homepage: http://astropy.org

Update matplotlib from 2.2.0 to 2.2.2.

Changelog
Links - PyPI: https://pypi.python.org/pypi/matplotlib - Changelog: https://pyup.io/changelogs/matplotlib/ - Homepage: http://matplotlib.org

Update numpy from 1.14.1 to 1.14.2.

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

Links - PyPI: https://pypi.python.org/pypi/numpy - Changelog: https://pyup.io/changelogs/numpy/ - Homepage: http://www.numpy.org

Update sqlalchemy from 1.2.4 to 1.2.5.

Changelog ### 1.2.5 ``` :released: March 6, 2018 .. change:: :tags: bug, sql :tickets: 4210 :versions: 1.3.0b1 Fixed bug in :class:.`CTE` construct along the same lines as that of :ticket:`4204` where a :class:`.CTE` that was aliased would not copy itself correctly during a "clone" operation as is frequent within the ORM as well as when using the :meth:`.ClauseElement.params` method. .. change:: :tags: bug, orm :tickets: 4199 Fixed bug in new "polymorphic selectin" loading when a selection of polymorphic objects were to be partially loaded from a relationship lazy loader, leading to an "empty IN" condition within the load that raises an error for the "inline" form of "IN". .. change:: :tags: bug, sql :tickets: 4204 Fixed bug in CTE rendering where a :class:`.CTE` that was also turned into an :class:`.Alias` would not render its "ctename AS aliasname" clause appropriately if there were more than one reference to the CTE in a FROM clause. .. change:: :tags: bug, orm :tickets: 4209 :versions: 1.3.0b1 Fixed 1.2 regression where a mapper option that contains an :class:`.AliasedClass` object, as is typical when using the :meth:`.QueryableAttribute.of_type` method, could not be pickled. 1.1's behavior was to omit the aliased class objects from the path, so this behavior is restored. .. change:: :tags: feature, orm :versions: 1.3.0b1 Added new feature :meth:`.Query.only_return_tuples`. Causes the :class:`.Query` object to return keyed tuple objects unconditionally even if the query is against a single entity. Pull request courtesy Eric Atkin. .. change:: :tags: bug, sql :tickets: 4198 Fixed bug in new "expanding IN parameter" feature where the bind parameter processors for values wasn't working at all, tests failed to cover this pretty basic case which includes that ENUM values weren't working. .. changelog:: ```
Links - PyPI: https://pypi.python.org/pypi/sqlalchemy - Changelog: https://pyup.io/changelogs/sqlalchemy/ - Homepage: http://www.sqlalchemy.org

Update tqdm from 4.19.6 to 4.19.8.

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

Links - PyPI: https://pypi.python.org/pypi/tqdm - Changelog: https://pyup.io/changelogs/tqdm/ - Repo: https://github.com/tqdm/tqdm/issues

Update hypothesis from 3.48.1 to 3.50.2.

Changelog ### 3.50.2 ``` ------------------- This has no user-visible changes except one slight formatting change to one docstring, to avoid a deprecation warning. ------------------- ``` ### 3.50.1 ``` ------------------- This patch fixes an internal error introduced in 3.48.0, where a check for the Django test runner would expose import-time errors in Django configuration (:issue:`1167`). ------------------- ``` ### 3.50.0 ``` ------------------- This release improves validation of numeric bounds for some strategies. - :func:`~hypothesis.strategies.integers` and :func:`~hypothesis.strategies.floats` now raise ``InvalidArgument`` if passed a ``min_value`` or ``max_value`` which is not an instance of :class:`~python:numbers.Real`, instead of various internal errors. - :func:`~hypothesis.strategies.floats` now converts its bounding values to the nearest float above or below the min or max bound respectively, instead of just casting to float. The old behaviour was incorrect in that you could generate ``float(min_value)``, even when this was less than ``min_value`` itself (possible with eg. fractions). - When both bounds are provided to :func:`~hypothesis.strategies.floats` but there are no floats in the interval, such as ``[(2**54)+1 .. (2**55)-1]``, InvalidArgument is raised. - :func:`~hypothesis.strategies.decimals` gives a more useful error message if passed a string that cannot be converted to :class:`~python:decimal.Decimal` in a context where this error is not trapped. Code that previously **seemed** to work may be explicitly broken if there were no floats between ``min_value`` and ``max_value`` (only possible with non-float bounds), or if a bound was not a :class:`~python:numbers.Real` number but still allowed in :obj:`python:math.isnan` (some custom classes with a ``__float__`` method). ------------------- ``` ### 3.49.1 ``` ------------------- This patch fixes our tests for Numpy dtype strategies on big-endian platforms, where the strategy behaved correctly but the test assumed that the native byte order was little-endian. There is no user impact unless you are running our test suite on big-endian platforms. Thanks to Graham Inggs for reporting :issue:`1164`. ------------------- ``` ### 3.49.0 ``` ------------------- This release deprecates passing ``elements=None`` to collection strategies, such as :func:`~hypothesis.strategies.lists`. Requiring ``lists(nothing())`` or ``builds(list)`` instead of ``lists()`` means slightly more typing, but also improves the consistency and discoverability of our API - as well as showing how to compose or construct strategies in ways that still work in more complex situations. Passing a nonzero max_size to a collection strategy where the elements strategy contains no values is now deprecated, and will be an error in a future version. The equivalent with ``elements=None`` is already an error. ------------------- ```
Links - PyPI: https://pypi.python.org/pypi/hypothesis - Changelog: https://pyup.io/changelogs/hypothesis/ - Repo: https://github.com/HypothesisWorks/hypothesis/issues
coveralls commented 6 years ago

Coverage Status

Coverage remained the same at 59.268% when pulling d0df272c5231fdd6d165ed38bd7c60b214c3a89a on pyup/scheduled-update-2018-03-20 into 44df9fb732d97f3fb886c249f80ec041032fa68c on develop.