coveralls
commented
5 years ago Coverage increased (+0.02%) to 55.948% when pulling 0f4634c936ca08fa349d12877e73e6ec7c4b7aa1 on pyup/scheduled-update-2019-07-01 into 3571af6c8c2c6a8c259999e7bd569696059940ad on develop.
pyup-bot
Update astropy from 3.1.2 to 3.2.1.
Changelog
### 3.2.1 ``` ================== Bug fixes --------- astropy.config ^^^^^^^^^^^^^^ astropy.constants ^^^^^^^^^^^^^^^^^ astropy.convolution ^^^^^^^^^^^^^^^^^^^ astropy.coordinates ^^^^^^^^^^^^^^^^^^^ astropy.cosmology ^^^^^^^^^^^^^^^^^ astropy.extern ^^^^^^^^^^^^^^ astropy.io.ascii ^^^^^^^^^^^^^^^^ astropy.io.misc ^^^^^^^^^^^^^^^ astropy.io.fits ^^^^^^^^^^^^^^^ - Avoid reporting a warning with ``BinTableHDU.from_columns`` with keywords that are not provided by the user. [8838] astropy.io.registry ^^^^^^^^^^^^^^^^^^^ astropy.io.votable ^^^^^^^^^^^^^^^^^^ astropy.modeling ^^^^^^^^^^^^^^^^ astropy.nddata ^^^^^^^^^^^^^^ astropy.samp ^^^^^^^^^^^^ astropy.stats ^^^^^^^^^^^^^ astropy.table ^^^^^^^^^^^^^ - Fix a problem where mask was dropped when creating a ``MaskedColumn`` from a list of ``MaskedArray`` objects. [8826] astropy.tests ^^^^^^^^^^^^^ astropy.time ^^^^^^^^^^^^ astropy.timeseries ^^^^^^^^^^^^^^^^^^ astropy.uncertainty ^^^^^^^^^^^^^^^^^^^ astropy.units ^^^^^^^^^^^^^ - Fixed a bug that prevented ``EarthLocation`` from being initialized with numpy >=1.17. [8849] astropy.utils ^^^^^^^^^^^^^ astropy.visualization ^^^^^^^^^^^^^^^^^^^^^ astropy.wcs ^^^^^^^^^^^ Other Changes and Additions --------------------------- ``` ### 3.2 ``` ================ New Features ------------ astropy.constants ^^^^^^^^^^^^^^^^^ - Add CODATA 2018 constants but not make them default because the redefinition of SI units that will follow has not been implemented yet. [8595] astropy.coordinates ^^^^^^^^^^^^^^^^^^^ - New ``BarycentricMeanEcliptic``, ``HeliocentricTrueEcliptic`` and ``GeocentricTrueEcliptic`` frames. The ecliptic frames are no longer considered experimental. [8394] - The default time scale for epochs like 'J2000' or 'B1975' is now "tt", which is the correct one for 'J2000' and avoids leap-second warnings for epochs in the far future or past. [8600] astropy.extern ^^^^^^^^^^^^^^ - Bundled ``six`` now emits ``AstropyDeprecationWarning``. It will be removed in 4.0. [8323] astropy.io.ascii ^^^^^^^^^^^^^^^^ - IPAC tables now output data types of ``float`` instead of ``double``, or ``int`` instead of ``long``, based on the column ``dtype.itemsize``. [8216] - Update handling of MaskedColumn columns when using the 'data_mask' serialization method. This can make writing ECSV significantly faster if the data do not actually have any masked values. [8447] - Fixed a bug that caused newlines to be incorrect when writing out ASCII tables on Windows (they were ``\r\r\n`` instead of ``\r\n``). [8659] astropy.io.misc ^^^^^^^^^^^^^^^ - Implement serialization of ``TimeDelta`` in ASDF. [8285] - Implement serialization of ``EarthLocation`` in ASDF. [8286] - Implement serialization of ``SkyCoord`` in ASDF. [8284] - Support serialization of Astropy tables with mixin columns in ASDF. [8337] - No warnings when reading HDF5 files with only one table and no ``path=`` argument [8483] - The HDF5 writer will now create a default table instead of raising an exception when ``path=`` is not specified and when writing to empty/new HDF5 files. [8553] astropy.io.fits ^^^^^^^^^^^^^^^ - Optimize parsing of cards within the ``Header`` class. [8428] - Optimize the parsing of headers to get the structural keywords that are needed to find extensions. Thanks to this, getting a random HDU from a file with many extensions is much faster than before, in particular when the extension headers contain many keywords. [8502] - Change behavior of FITS undefined value in ``Header`` such that ``None`` is used in Python to represent FITS undefined when using dict interface. ``Undefined`` can also be assigned and is translated to ``None``. Previously setting a header card value to ``None`` resulted in an empty string field rather than a FITS undefined value. [8572] - Allow ``Header.fromstring`` and ``Card.fromstring`` to accept ``bytes``. [8707] astropy.io.registry ^^^^^^^^^^^^^^^^^^^ - Implement ``Table`` reader and writer for ``ASDF``. [8261] - Implement ``Table`` reader and writer methods to wrap ``pandas`` I/O methods for CSV, Fixed width format, HTML, and JSON. [8381] - Add ``help()`` and ``list_formats()`` methods to unified I/O ``read`` and ``write`` methods. For example ``Table.read.help()`` gives help on available ``Table`` read formats and ``Table.read.help('fits')`` gives detailed help on the arguments for reading FITS table file. [8255] astropy.table ^^^^^^^^^^^^^ - Initializing a table with ``Table(rows=...)``, if the first item is an ``OrderedDict``, now uses the column order of the first row. [8587] - Added new pprint_all() and pformat_all() methods to Table. These two new methods print the entire table by default. [8577] - Removed restriction of initializing a Table from a dict with copy=False. [8541] - Improved speed of table row access by a factor of about 2-3. Improved speed of Table len() by a factor of around 3-10 (depending on the number of columns). [8494] - Improved the Table - pandas ``DataFrame`` interface (``to_pandas()`` and ``from_pandas()``). Mixin columns like ``Time`` and ``Quantity`` can now be converted to pandas by flattening the columns as necessary to plain columns. ``Time`` and ``TimeDelta`` columns get converted to corresponding pandas date or time delta types. The ``DataFrame`` index is now handled in the conversion methods. [8247] - Added ``rename_columns`` method to rename multiple columns in one call. [5159, 8070] - Improved Table performance by reducing unnecessary calls to copy and deepcopy, especially as related to the table and column ``meta`` attributes. Changed the behavior when slicing a table (either in rows or with a list of column names) so now the sliced output gets a light (key-only) copy of ``meta`` instead of a deepcopy. Changed the ``Table.meta`` class-level descriptor so that assigning directly to ``meta``, e.g. ``tbl.meta = new_meta`` no longer does a deepcopy and instead just directly assigns the ``new_meta`` object reference. Changed Table initialization so that input ``meta`` is copied only if ``copy=True``. [8404] - Improved Table slicing performance with internal implementation changes related to column attribute access and certain input validation. [8493] - Added ``reverse`` argument to the ``sort`` and ``argsort`` methods to allow sorting in reverse order. [8528] - Improved ``Table.sort()`` performance by removing ``self[keys]`` from code which is creating deep copies of ``meta`` attribute and adding a new keyword ``names`` in ``get_index()`` to get index by using a list or tuple containing names of columns. [8570] - Expose ``represent_mixins_as_columns`` as a public function in the ``astropy.table`` subpackage. This previously-private function in the ``table.serialize`` module is used to represent mixin columns in a Table as one or more plain Column objects. [7729] astropy.timeseries ^^^^^^^^^^^^^^^^^^ - Added a new astropy.timeseries sub-package to represent and manipulate sampled and binned time series. [8540] - The ``BoxLeastSquares`` and ``LombScargle`` classes have been moved to ``astropy.timeseries.periodograms`` from ``astropy.stats``. [8591] - Added the ability to provide absolute ``Time`` objects to the ``BoxLeastSquares`` and ``LombScargle`` periodogram classes. [8599] - Added model inspection methods (``model_parameters()``, ``design_matrix()``, and ``offset()``) to ``astropy.timeseries.LombScargle`` class [8397]. astropy.units ^^^^^^^^^^^^^ - ``Quantity`` overrides of ``ndarray`` methods such as ``sum``, ``min``, ``max``, which are implemented via reductions, have been removed since they are dealt with in ``Quantity.__array_ufunc__``. This should not affect subclasses, but they may consider doing similarly. [8316] Note that this does not include methods that use more complicated python code such as ``mean``, ``std`` and ``var``. [8370] astropy.visualization ^^^^^^^^^^^^^^^^^^^^^ - Added ``CompositeStretch``, which inherits from ``CompositeTransform`` and also ``BaseStretch`` so that it can be used with ``ImageNormalize``. [8564] - Added a ``log_a`` argument to the ``simple_norm`` method. Similar to the exposing of the ``asinh_a`` argument for ``AsinhStretch``, the new ``log_a`` argument is now exposed for ``LogStretch``. [8436] astropy.wcs ^^^^^^^^^^^ - WCSLIB was updated to v 6.2. This adds support for time-related WCS keywords (WCS Paper VII). FITS headers containing ``Time`` axis are parsed and the axis is included in the WCS object. [8592] - The ``OBSGEO`` attribute as expanded to 6 members - ``XYZLBH``. [8592] - Added a new class ``SlicedLowLevelWCS`` in ``astropy.wcs.wcsapi`` that can be used to slice any WCS that conforms to the ``BaseLowLevelWCS`` API. [8546] - Updated implementation of ``WCS.__getitem__`` and ``WCS.slice`` to now return a ``SlicedLowLevelWCS`` rather than raising an error when reducing the dimensionality of the WCS. [8546] API Changes ----------- astropy.coordinates ^^^^^^^^^^^^^^^^^^^ - ``QuantityAttribute`` no longer has a default value for ``default``. The previous value of None was misleading as it always was an error. [8450] - The default J2000 has been changed to use be January 1, 2000 12:00 TT instead of UTC. This is more in line with convention. [8594] astropy.io.ascii ^^^^^^^^^^^^^^^^ - IPAC tables now output data types of ``float`` instead of ``double``, or ``int`` instead of ``long``, based on the column ``dtype.itemsize``. [8216] astropy.io.misc ^^^^^^^^^^^^^^^ - Unit equivalencies can now be serialized to ASDF. [8252] astropy.modeling ^^^^^^^^^^^^^^^^ - Composition of model classes is deprecated and will be removed in 4.0. Composition of model instances remain unaffected. [8234, 8408] astropy.stats ^^^^^^^^^^^^^ - The ``BoxLeastSquares`` and ``LombScargle`` classes have been moved to the ``astropy.timeseries.periodograms`` module and will now emit a deprecation warning when imported from ``astropy.stats``. [8591] astropy.table ^^^^^^^^^^^^^ - Converting an empty table to an array using ``as_array`` method now returns an empty array instead of ``None``. [8647] - Changed the behavior when slicing a table (either in rows or with a list of column names) so now the sliced output gets a light (key-only) copy of ``meta`` instead of a deepcopy. Changed the ``Table.meta`` class-level descriptor so that assigning directly to ``meta``, e.g. ``tbl.meta = new_meta`` no longer does a deepcopy and instead just directly assigns the ``new_meta`` object reference. Changed Table initialization so that input ``meta`` is copied only if ``copy=True``. [8404] - Added a keyword ``names`` in ``Table.as_array()``. If provided this specifies a list of column names to include for the returned structured array. [8532] astropy.tests ^^^^^^^^^^^^^ - Removed ``pytest_plugins`` as they are completely broken for ``pytest>=4``. [7786] - Removed the ``astropy.tests.plugins.config`` plugin and removed the ``--astropy-config-dir`` and ``--astropy-cache-dir`` options from testing. Please use caching functionality that is natively in ``pytest``. [7787, 8489] astropy.time ^^^^^^^^^^^^ - The default time scale for epochs like 'J2000' or 'B1975' is now "tt", which is the correct one for 'J2000' and avoids leap-second warnings for epochs in the far future or past. [8600] astropy.units ^^^^^^^^^^^^^ - Unit equivalencies can now be introspected. [8252] astropy.wcs ^^^^^^^^^^^ - The ``world_to_pixel``, ``world_to_array_index*``, ``pixel_to_world*`` and ``array_index_to_world*`` methods now all consistently return scalars, arrays, or objects not wrapped in a one-element tuple/list when only one scalar, array, or object (as was previously already the case for ``WCS.pixel_to_world`` and ``WCS.array_index_to_world``). [8663] astropy.utils ^^^^^^^^^^^^^ - It is now possible to control the number of cores used by ``ProgressBar.map`` by passing a positive integer as the ``multiprocess`` keyword argument. Use ``True`` to use all cores. [8083] Bug Fixes --------- astropy.coordinates ^^^^^^^^^^^^^^^^^^^ - ``BarycentricTrueEcliptic``, ``HeliocentricTrueEcliptic`` and ``GeocentricTrueEcliptic`` now use the correct transformation (including nutation), whereas the new ``*MeanEcliptic`` classes use the nutation-free transformation. [8394] - Representations with ``float32`` coordinates can now be transformed, although the output will always be ``float64``. [8759] - Fixed bug that prevented using differentials with HCRS<->ICRS transformations. [8794] astropy.io.ascii ^^^^^^^^^^^^^^^^ - Fixed a bug where an exception was raised when writing a table which includes mixin columns (e.g. a Quantity column) and the output format was specified using the ``formats`` keyword. [8681] astropy.io.misc ^^^^^^^^^^^^^^^ - Fixed bug in ASDF tag that inadvertently introduced dependency on ``pytest``. [8456] astropy.modeling ^^^^^^^^^^^^^^^^ - Fixed slowness for certain compound models consisting of large numbers of multi-input models [8338, 8349] - Fixed bugs in fitting of compound models with units. [8369] astropy.nddata ^^^^^^^^^^^^^^ - Fixed bug in reading multi-extension FITS files written by earlier versions of ``CCDData``. [8534] - Fixed two errors in the way ``CCDData`` handles FITS files with WCS in the header. Some of the WCS keywords that should have been removed from the header were not, potentially leading to FITS files with inconsistent WCS. [8602] astropy.table ^^^^^^^^^^^^^ - Fixed a bug when initializing from an empty list: ``Table([])`` no longer results in a crash. [8647] - Fixed a bug when initializing from an existing ``Table``. In this case the input ``meta`` argument was being ignored. Now the input ``meta``, if supplied, will be used as the ``meta`` for the new ``Table``. [8404] - Fix the conversion of bytes values to Python ``str`` with ``Table.tolist``. [8739] astropy.time ^^^^^^^^^^^^ - Fixed a number of issues to ensure a consistent output type resulting from multiplication or division involving a ``TimeDelta`` instance. The output is now always a ``TimeDelta`` if the result is a time unit (like u.s or u.d), otherwise it will be a ``Quantity``. [8356] - Multiplication between two ``TimeDelta`` instances is now possible, resulting in a ``Quantity`` with units of time squared (division already correctly resulted in a dimensionless ``Quantity``). [8356] - Like for comparisons, addition, and subtraction of ``Time`` instances with with non-time instances, multiplication and division of ``TimeDelta`` instances with incompatible other instances no longer immediately raise an ``UnitsError`` or ``TypeError`` (depending on the other instance), but rather go through the regular Python mechanism of ``TimeDelta`` returning ``NotImplemented`` (which will lead to a regular ``TypeError`` unless the other instance can handle ``TimeDelta``). [8356] - Corrected small rounding errors that could cause the ``jd2`` values in ``Time`` to fall outside the range of -0.5 to 0.5. [8763] astropy.units ^^^^^^^^^^^^^ - Added a ``Quantity.to_string`` method to add flexibility to the string formatting of quantities. It produces unadorned or LaTeX strings, and accepts two different sets of delimiters in the latter case: ``inline`` and ``display``. [8313] - Ensure classes that mimic quantities by having a ``unit`` attribute and/or ``to`` and ``to_value`` methods can be properly used to initialize ``Quantity`` or set ``Quantity`` instance items. [8535] - Add support for ``<<`` to create logarithmic units. [8290] - Add support for the ``clip`` ufunc, which in numpy 1.17 is used to implement ``np.clip``. As part of that, remove the ``Quantity.clip`` method under numpy 1.17. [8747] - Fix parsing of numerical powers in FITS-compatible units. [8251] astropy.wcs ^^^^^^^^^^^ - Added a ``PyUnitListProxy_richcmp`` method in ``UnitListProxy`` class to enable ``WCS.wcs.cunit`` equality testing. It helps to check whether the two instances of ``WCS.wcs.cunit`` are equal or not by comparing the data members of ``UnitListProxy`` class [8480] - Fixed ``SlicedLowLevelWCS`` when ``array_shape`` is ``None``. [8649] - Do not attempt to delete repeated distortion keywords multiple times when loading distortions with ``_read_distortion_kw`` and ``_read_det2im_kw``. [8777] - Added ``None`` to be displayed as a ``world_axis_physical_types`` in the ``WCS`` repr, as ``None`` values are now supported in ``APE14``. [8811] Other Changes and Additions --------------------------- - Update bundled expat to 2.2.6. [8343] - Added instructions for uploading releases to Zenodo. [8395] - The bug fixes to the behaviour of ``TimeDelta`` for multiplcation and division, which ensure that the output is now always a ``TimeDelta`` if the result is a time unit (like u.s or u.d) and otherwise a ``Quantity``, imply that sometimes the output type will be different than it was before. [8356] - For types unrecognized by ``TimeDelta``, multiplication and division now will consistently return a ``TypeError`` if the other instance cannot handle ``TimeDelta`` (rather than ``UnitsError`` or ``TypeError`` depending on presumed abilities of the other instance). [8356] - Multiplication between two ``TimeDelta`` instances will no longer result in an ``OperandTypeError``, but rather result in a ``Quantity`` with units of time squared (division already correctly resulted in a dimensionless ``Quantity``). [8356] - Made running the tests insensitive to local user configuration when running the tests in parallel mode or directly with pytest. [8727] - Added a narrative style guide to the documentation for contributor reference. [8588] - Ensure we call numpy equality functions in a way that reduces the number of ``DeprecationWarning``. [8755] Installation ^^^^^^^^^^^^ - We now require setuptools 30.3.0 or later to install the core astropy package. [8240] - We now define groups of dependencies that can be installed with pip, e.g. ``pip install astropy[all]`` (to install all optional dependencies). [8198] ```Links
- PyPI: https://pypi.org/project/astropy - Changelog: https://pyup.io/changelogs/astropy/ - Homepage: http://astropy.orgUpdate matplotlib from 3.0.3 to 3.1.0.
Changelog
Links
- PyPI: https://pypi.org/project/matplotlib - Changelog: https://pyup.io/changelogs/matplotlib/ - Homepage: https://matplotlib.orgUpdate numba from 0.43.1 to 0.44.1.
Changelog
### 0.44.1 ``` -------------- This patch release addresses some regressions reported in the 0.44.0 release: - PR 4165: Fix 4164 issue with NUMBAPRO_NVVM. - PR 4172: Abandon branch pruning if an arg name is redefined. (Fixes 4163) - PR 4183: Fix 4156. Problem with defining in-loop variables. ``` ### 0.44.0 ``` -------------- IMPORTANT: In this release a few significant deprecations (and some less significant ones) are being made, users are encouraged to read the related documentation. General enhancements in this release include: - Numba is backed by LLVM 8 on all platforms apart from ppc64le, which, due to bugs, remains on the LLVM 7.x series. - Numba's dictionary support now includes type inference for keys and values. - The .view() method now works for NumPy scalar types. - Newly supported NumPy functions added: np.delete, np.nanquantile, np.quantile, np.repeat, np.shape. In addition considerable effort has been made to fix some long standing bugs and a large number of other bugs, the "Fixes" section is very large this time! Enhancements from user contributed PRs (with thanks!): - Max Bolingbroke added support for the selective use of ``fastmath`` flags in 3847. - Rob Ennis made min() and max() work on iterables in 3820 and added np.quantile and np.nanquantile in 3899. - Sergey Shalnov added numerous unicode string related features, zfill in 3978, ljust in 4001, rjust and center in 4044 and strip, lstrip and rstrip in 4048. - Guilherme Leobas added support for np.delete in 3890 - Christoph Deil exposed the Numba CLI via ``python -m numba`` in 4066 and made numerous documentation fixes. - Leo Schwarz wrote the bulk of the code for jitclass default constructor arguments in 3852. - Nick White enhanced the CUDA backend to use min/max PTX instructions where possible in 4054. - Lucio Fernandez-Arjona implemented the unicode string ``__mul__`` function in 3952. - Dimitri Vorona wrote the bulk of the code to implement getitem and setitem for jitclass in 3861. General Enhancements: * PR 3820: Min max on iterables * PR 3842: Unicode type iteration * PR 3847: Allow fine-grained control of fastmath flags to partially address 2923 * PR 3852: Continuation of PR 2894 * PR 3861: Continuation of PR 3730 * PR 3890: Add support for np.delete * PR 3899: Support for np.quantile and np.nanquantile * PR 3900: Fix 3457 :: Implements np.repeat * PR 3928: Add .view() method for NumPy scalars * PR 3939: Update icc_rt clone recipe. * PR 3952: __mul__ for strings, initial implementation and tests * PR 3956: Type-inferred dictionary * PR 3959: Create a view for string slicing to avoid extra allocations * PR 3978: zfill operation implementation * PR 4001: ljust operation implementation * PR 4010: Support `dict()` and `{}` * PR 4022: Support for llvm 8 * PR 4034: Make type.Optional str more representative * PR 4041: Deprecation warnings * PR 4044: rjust and center operations implementation * PR 4048: strip, lstrip and rstrip operations implementation * PR 4066: Expose numba CLI via python -m numba * PR 4081: Impl `np.shape` and support function for `asarray`. * PR 4091: Deprecate the use of iternext_impl without RefType CUDA Enhancements/Fixes: * PR 3933: Adds `.nbytes` property to CUDA device array objects. * PR 4011: Add .inspect_ptx() to cuda device function * PR 4054: CUDA: Use min/max PTX Instructions * PR 4096: Update env-vars for CUDA libraries lookup Documentation Updates: * PR 3867: Code repository map * PR 3918: adding Joris' Fosdem 2019 presentation * PR 3926: order talks on applications of Numba by date * PR 3943: fix two small typos in vectorize docs * PR 3944: Fixup jitclass docs * PR 3990: mention preprint repo in FAQ. Fixes 3981 * PR 4012: Correct runtests command in contributing.rst * PR 4043: fix typo * PR 4047: Ambiguous Documentation fix for guvectorize. * PR 4060: Remove remaining mentions of autojit in docs * PR 4063: Fix annotate example in docstring * PR 4065: Add FAQ entry explaining Numba project name * PR 4079: Add Documentation for atomicity of typed.Dict * PR 4105: Remove info about CUDA ENVVAR potential replacement Fixes: * PR 3719: Resolves issue 3528. Adds support for slices when not using parallel=True. * PR 3727: Remove dels for known dead vars. * PR 3845: Fix mutable flag transmission in .astype * PR 3853: Fix some minor issues in the C source. * PR 3862: Correct boolean reinterpretation of data * PR 3863: Comments out the appveyor badge * PR 3869: fixes flake8 after merge * PR 3871: Add assert to ir.py to help enforce correct structuring * PR 3881: fix preparfor dtype transform for datetime64 * PR 3884: Prevent mutation of objmode fallback IR. * PR 3885: Updates for llvmlite 0.29 * PR 3886: Use `safe_load` from pyyaml. * PR 3887: Add tolerance to network errors by permitting conda to retry * PR 3893: Fix casting in namedtuple ctor. * PR 3894: Fix array inliner for multiple array definition. * PR 3905: Cherrypick 3903 to main * PR 3920: Raise better error if unsupported jump opcode found. * PR 3927: Apply flake8 to the numpy related files * PR 3935: Silence DeprecationWarning * PR 3938: Better error message for unknown opcode * PR 3941: Fix typing of ufuncs in parfor conversion * PR 3946: Return variable renaming dict from inline_closurecall * PR 3962: Fix bug in alignment computation of `Record.make_c_struct` * PR 3967: Fix error with pickling unicode * PR 3964: Unicode split algo versioning * PR 3975: Add handler for unknown locale to numba -s * PR 3991: Permit Optionals in ufunc machinery * PR 3995: Remove assert in type inference causing poor error message. * PR 3996: add is_ascii flag to UnicodeType * PR 4009: Prevent zero division error in np.linalg.cond * PR 4014: Resolves 4007. * PR 4021: Add a more specific error message for invalid write to a global. * PR 4023: Fix handling of titles in record dtype * PR 4024: Do a check if a call is const before saying that an object is multiply defined. * PR 4027: Fix issue 4020. Turn off no_cpython_wrapper flag when compiling for… * PR 4033: [WIP] Fixing wrong dtype of array inside reflected list 4028 * PR 4061: Change IPython cache dir name to numba_cache * PR 4067: Delete examples/notebooks/LinearRegr.py * PR 4070: Catch writes to global typed.Dict and raise. * PR 4078: Check tuple length * PR 4084: Fix missing incref on optional return None * PR 4089: Make the warnings fixer flush work for warning comparing on type. * PR 4094: Fix function definition finding logic for commented def * PR 4100: Fix alignment check on 32-bit. * PR 4104: Use PEP 508 compliant env markers for install deps Contributors: * Benjamin Zaitlen * Christoph Deil * David Hirschfeld * Dimitri Vorona * Ehsan Totoni (core dev) * Guilherme Leobas * Leo Schwarz * Lucio Fernandez-Arjona * Max Bolingbroke * NanduTej * Nick White * Ravi Teja Gutta * Rob Ennis * Sergey Shalnov * Siu Kwan Lam (core dev) * Stan Seibert (core dev) * Stuart Archibald (core dev) * Todd A. Anderson (core dev) * Valentin Haenel (core dev) ```Links
- PyPI: https://pypi.org/project/numba - Changelog: https://pyup.io/changelogs/numba/ - Repo: http://numba.github.comUpdate numpy from 1.16.2 to 1.16.4.
Changelog
### 1.16.4 ``` ========================== The NumPy 1.16.4 release fixes bugs reported against the 1.16.3 release, and also backports several enhancements from master that seem appropriate for a release series that is the last to support Python 2.7. The wheels on PyPI are linked with OpenBLAS v0.3.7-dev, which should fix issues on Skylake series cpus. Downstream developers building this release should use Cython >= 0.29.2 and, if using OpenBLAS, OpenBLAS > v0.3.7. The supported Python versions are 2.7 and 3.5-3.7. New deprecations ================ Writeable flag of C-API wrapped arrays -------------------------------------- When an array is created from the C-API to wrap a pointer to data, the only indication we have of the read-write nature of the data is the ``writeable`` flag set during creation. It is dangerous to force the flag to writeable. In the future it will not be possible to switch the writeable flag to ``True`` from python. This deprecation should not affect many users since arrays created in such a manner are very rare in practice and only available through the NumPy C-API. Compatibility notes =================== Potential changes to the random stream -------------------------------------- Due to bugs in the application of log to random floating point numbers, the stream may change when sampling from ``np.random.beta``, ``np.random.binomial``, ``np.random.laplace``, ``np.random.logistic``, ``np.random.logseries`` or ``np.random.multinomial`` if a 0 is generated in the underlying MT19937 random stream. There is a 1 in :math:`10^{53}` chance of this occurring, and so the probability that the stream changes for any given seed is extremely small. If a 0 is encountered in the underlying generator, then the incorrect value produced (either ``np.inf`` or ``np.nan``) is now dropped. Changes ======= `numpy.lib.recfunctions.structured_to_unstructured` does not squeeze single-field views --------------------------------------------------------------------------------------- Previously ``structured_to_unstructured(arr[['a']])`` would produce a squeezed result inconsistent with ``structured_to_unstructured(arr[['a', b']])``. This was accidental. The old behavior can be retained with ``structured_to_unstructured(arr[['a']]).squeeze(axis=-1)`` or far more simply, ``arr['a']``. Contributors ============ A total of 10 people contributed to this release. People with a "+" by their names contributed a patch for the first time. * Charles Harris * Eric Wieser * Dennis Zollo + * Hunter Damron + * Jingbei Li + * Kevin Sheppard * Matti Picus * Nicola Soranzo + * Sebastian Berg * Tyler Reddy Pull requests merged ==================== A total of 16 pull requests were merged for this release. * `13392 <https://github.com/numpy/numpy/pull/13392>`__: BUG: Some PyPy versions lack PyStructSequence_InitType2. * `13394 <https://github.com/numpy/numpy/pull/13394>`__: MAINT, DEP: Fix deprecated ``assertEquals()`` * `13396 <https://github.com/numpy/numpy/pull/13396>`__: BUG: Fix structured_to_unstructured on single-field types (backport) * `13549 <https://github.com/numpy/numpy/pull/13549>`__: BLD: Make CI pass again with pytest 4.5 * `13552 <https://github.com/numpy/numpy/pull/13552>`__: TST: Register markers in conftest.py. * `13559 <https://github.com/numpy/numpy/pull/13559>`__: BUG: Removes ValueError for empty kwargs in arraymultiter_new * `13560 <https://github.com/numpy/numpy/pull/13560>`__: BUG: Add TypeError to accepted exceptions in crackfortran. * `13561 <https://github.com/numpy/numpy/pull/13561>`__: BUG: Handle subarrays in descr_to_dtype * `13562 <https://github.com/numpy/numpy/pull/13562>`__: BUG: Protect generators from log(0.0) * `13563 <https://github.com/numpy/numpy/pull/13563>`__: BUG: Always return views from structured_to_unstructured when... * `13564 <https://github.com/numpy/numpy/pull/13564>`__: BUG: Catch stderr when checking compiler version * `13565 <https://github.com/numpy/numpy/pull/13565>`__: BUG: longdouble(int) does not work * `13587 <https://github.com/numpy/numpy/pull/13587>`__: BUG: distutils/system_info.py fix missing subprocess import (13523) * `13620 <https://github.com/numpy/numpy/pull/13620>`__: BUG,DEP: Fix writeable flag setting for arrays without base * `13641 <https://github.com/numpy/numpy/pull/13641>`__: MAINT: Prepare for the 1.16.4 release. * `13644 <https://github.com/numpy/numpy/pull/13644>`__: BUG: special case object arrays when printing rel-, abs-error ========================== ``` ### 1.16.3 ``` ========================== The NumPy 1.16.3 release fixes bugs reported against the 1.16.2 release, and also backports several enhancements from master that seem appropriate for a release series that is the last to support Python 2.7. The wheels on PyPI are linked with OpenBLAS v0.3.4+, which should fix the known threading issues found in previous OpenBLAS versions. Downstream developers building this release should use Cython >= 0.29.2 and, if using OpenBLAS, OpenBLAS > v0.3.4. The most noticeable change in this release is that unpickling object arrays when loading ``*.npy`` or ``*.npz`` files now requires an explicit opt-in. This backwards incompatible change was made in response to `CVE-2019-6446 <https://nvd.nist.gov/vuln/detail/CVE-2019-6446>`_. Compatibility notes =================== Unpickling while loading requires explicit opt-in ------------------------------------------------- The functions ``np.load``, and ``np.lib.format.read_array`` take an `allow_pickle` keyword which now defaults to ``False`` in response to `CVE-2019-6446 <https://nvd.nist.gov/vuln/detail/CVE-2019-6446>`_. Improvements ============ Covariance in `random.mvnormal` cast to double ---------------------------------------------- This should make the tolerance used when checking the singular values of the covariance matrix more meaningful. Changes ======= ``__array_interface__`` offset now works as documented ------------------------------------------------------ The interface may use an ``offset`` value that was previously mistakenly ignored. ========================== ```Links
- PyPI: https://pypi.org/project/numpy - Changelog: https://pyup.io/changelogs/numpy/ - Homepage: https://www.numpy.orgUpdate multiprocess from 0.70.7 to 0.70.8.
The bot wasn't able to find a changelog for this release. Got an idea?
Links
- PyPI: https://pypi.org/project/multiprocess - Changelog: https://pyup.io/changelogs/multiprocess/ - Repo: https://github.com/uqfoundation/multiprocess/releases/download/multiprocess-0.70.8/multiprocess-0.70.8.tar.gz - Homepage: https://pypi.org/project/multiprocessUpdate scipy from 1.2.1 to 1.3.0.
Changelog
### 1.3.0 ``` many new features, numerous bug-fixes, improved test coverage and better documentation. There have been some API changes in this release, which are documented below. All users are encouraged to upgrade to this release, as there are a large number of bug-fixes and optimizations. Before upgrading, we recommend that users check that their own code does not use deprecated SciPy functionality (to do so, run your code with ``python -Wd`` and check for ``DeprecationWarning`` s). Our development attention will now shift to bug-fix releases on the 1.3.x branch, and on adding new features on the master branch. This release requires Python 3.5+ and NumPy 1.13.3 or greater. For running on PyPy, PyPy3 6.0+ and NumPy 1.15.0 are required. Highlights of this release -------------------------- - Three new ``stats`` functions, a rewrite of ``pearsonr``, and an exact computation of the Kolmogorov-Smirnov two-sample test - A new Cython API for bounded scalar-function root-finders in `scipy.optimize` - Substantial ``CSR`` and ``CSC`` sparse matrix indexing performance improvements - Added support for interpolation of rotations with continuous angular rate and acceleration in ``RotationSpline`` New features ============ `scipy.interpolate` improvements -------------------------------- A new class ``CubicHermiteSpline`` is introduced. It is a piecewise-cubic interpolator which matches observed values and first derivatives. Existing cubic interpolators ``CubicSpline``, ``PchipInterpolator`` and ``Akima1DInterpolator`` were made subclasses of ``CubicHermiteSpline``. `scipy.io` improvements ----------------------- For the Attribute-Relation File Format (ARFF) `scipy.io.arff.loadarff` now supports relational attributes. `scipy.io.mmread` can now parse Matrix Market format files with empty lines. `scipy.linalg` improvements --------------------------- Added wrappers for ``?syconv`` routines, which convert a symmetric matrix given by a triangular matrix factorization into two matrices and vice versa. `scipy.linalg.clarkson_woodruff_transform` now uses an algorithm that leverages sparsity. This may provide a 60-90 percent speedup for dense input matrices. Truly sparse input matrices should also benefit from the improved sketch algorithm, which now correctly runs in ``O(nnz(A))`` time. Added new functions to calculate symmetric Fiedler matrices and Fiedler companion matrices, named `scipy.linalg.fiedler` and `scipy.linalg.fiedler_companion`, respectively. These may be used for root finding. `scipy.ndimage` improvements ---------------------------- Gaussian filter performances may improve by an order of magnitude in some cases, thanks to removal of a dependence on ``np.polynomial``. This may impact `scipy.ndimage.gaussian_filter` for example. `scipy.optimize` improvements ----------------------------- The `scipy.optimize.brute` minimizer obtained a new keyword ``workers``, which can be used to parallelize computation. A Cython API for bounded scalar-function root-finders in `scipy.optimize` is available in a new module `scipy.optimize.cython_optimize` via ``cimport``. This API may be used with ``nogil`` and ``prange`` to loop over an array of function arguments to solve for an array of roots more quickly than with pure Python. ``'interior-point'`` is now the default method for ``linprog``, and ``'interior-point'`` now uses SuiteSparse for sparse problems when the required scikits (scikit-umfpack and scikit-sparse) are available. On benchmark problems (gh-10026), execution time reductions by factors of 2-3 were typical. Also, a new ``method='revised simplex'`` has been added. It is not as fast or robust as ``method='interior-point'``, but it is a faster, more robust, and equally accurate substitute for the legacy ``method='simplex'``. ``differential_evolution`` can now use a ``Bounds`` class to specify the bounds for the optimizing argument of a function. `scipy.optimize.dual_annealing` performance improvements related to vectorisation of some internal code. `scipy.signal` improvements --------------------------- Two additional methods of discretization are now supported by `scipy.signal.cont2discrete`: ``impulse`` and ``foh``. `scipy.signal.firls` now uses faster solvers `scipy.signal.detrend` now has a lower physical memory footprint in some cases, which may be leveraged using the new ``overwrite_data`` keyword argument `scipy.signal.firwin` ``pass_zero`` argument now accepts new string arguments that allow specification of the desired filter type: ``'bandpass'``, ``'lowpass'``, ``'highpass'``, and ``'bandstop'`` `scipy.signal.sosfilt` may have improved performance due to lower retention of the global interpreter lock (GIL) in algorithm `scipy.sparse` improvements --------------------------- A new keyword was added to ``csgraph.dijsktra`` that allows users to query the shortest path to ANY of the passed in indices, as opposed to the shortest path to EVERY passed index. `scipy.sparse.linalg.lsmr` performance has been improved by roughly 10 percent on large problems Improved performance and reduced physical memory footprint of the algorithm used by `scipy.sparse.linalg.lobpcg` ``CSR`` and ``CSC`` sparse matrix fancy indexing performance has been improved substantially `scipy.spatial` improvements ---------------------------- `scipy.spatial.ConvexHull` now has a ``good`` attribute that can be used alongsize the ``QGn`` Qhull options to determine which external facets of a convex hull are visible from an external query point. `scipy.spatial.cKDTree.query_ball_point` has been modernized to use some newer Cython features, including GIL handling and exception translation. An issue with ``return_sorted=True`` and scalar queries was fixed, and a new mode named ``return_length`` was added. ``return_length`` only computes the length of the returned indices list instead of allocating the array every time. `scipy.spatial.transform.RotationSpline` has been added to enable interpolation of rotations with continuous angular rates and acceleration `scipy.stats` improvements -------------------------- Added a new function to compute the Epps-Singleton test statistic, `scipy.stats.epps_singleton_2samp`, which can be applied to continuous and discrete distributions. New functions `scipy.stats.median_absolute_deviation` and `scipy.stats.gstd` (geometric standard deviation) were added. The `scipy.stats.combine_pvalues` method now supports ``pearson``, ``tippett`` and ``mudholkar_george`` pvalue combination methods. The `scipy.stats.ortho_group` and `scipy.stats.special_ortho_group` ``rvs(dim)`` functions' algorithms were updated from a ``O(dim^4)`` implementation to a ``O(dim^3)`` which gives large speed improvements for ``dim>100``. A rewrite of `scipy.stats.pearsonr` to use a more robust algorithm, provide meaningful exceptions and warnings on potentially pathological input, and fix at least five separate reported issues in the original implementation. Improved the precision of ``hypergeom.logcdf`` and ``hypergeom.logsf``. Added exact computation for Kolmogorov-Smirnov (KS) two-sample test, replacing the previously approximate computation for the two-sided test `stats.ks_2samp`. Also added a one-sided, two-sample KS test, and a keyword ``alternative`` to `stats.ks_2samp`. Backwards incompatible changes ============================== `scipy.interpolate` changes --------------------------- Functions from ``scipy.interpolate`` (``spleval``, ``spline``, ``splmake``, and ``spltopp``) and functions from ``scipy.misc`` (``bytescale``, ``fromimage``, ``imfilter``, ``imread``, ``imresize``, ``imrotate``, ``imsave``, ``imshow``, ``toimage``) have been removed. The former set has been deprecated since v0.19.0 and the latter has been deprecated since v1.0.0. Similarly, aliases from ``scipy.misc`` (``comb``, ``factorial``, ``factorial2``, ``factorialk``, ``logsumexp``, ``pade``, ``info``, ``source``, ``who``) which have been deprecated since v1.0.0 are removed. `SciPy documentation for ```Links
- PyPI: https://pypi.org/project/scipy - Changelog: https://pyup.io/changelogs/scipy/ - Repo: https://github.com/scipy/scipy/releases - Homepage: https://www.scipy.orgUpdate sqlalchemy from 1.3.1 to 1.3.5.
Changelog
### 1.3.5 ``` :released: June 17, 2019 .. change:: :tags: bug, mysql :tickets: 4715 Fixed bug where MySQL ON DUPLICATE KEY UPDATE would not accommodate setting a column to the value NULL. Pull request courtesy Lukáš Banič. .. change:: :tags: bug, orm :tickets: 4723 Fixed a series of related bugs regarding joined table inheritance more than two levels deep, in conjunction with modification to primary key values, where those primary key columns are also linked together in a foreign key relationship as is typical for joined table inheritance. The intermediary table in a three-level inheritance hierachy will now get its UPDATE if only the primary key value has changed and passive_updates=False (e.g. foreign key constraints not being enforced), whereas before it would be skipped; similarly, with passive_updates=True (e.g. ON UPDATE CASCADE in effect), the third-level table will not receive an UPDATE statement as was the case earlier which would fail since CASCADE already modified it. In a related issue, a relationship linked to a three-level inheritance hierarchy on the primary key of an intermediary table of a joined-inheritance hierarchy will also correctly have its foreign key column updated when the parent object's primary key is modified, even if that parent object is a subclass of the linked parent class, whereas before these classes would not be counted. .. change:: :tags: bug, orm :tickets: 4729 Fixed bug where the :attr:`.Mapper.all_orm_descriptors` accessor would return an entry for the :class:`.Mapper` itself under the declarative ``__mapper___`` key, when this is not a descriptor. The ``.is_attribute`` flag that's present on all :class:`.InspectionAttr` objects is now consulted, which has also been modified to be ``True`` for an association proxy, as it was erroneously set to False for this object. .. change:: :tags: bug, orm :tickets: 4704 Fixed regression in :meth:`.Query.join` where the ``aliased=True`` flag would not properly apply clause adaptation to filter criteria, if a previous join were made to the same entity. This is because the adapters were placed in the wrong order. The order has been reversed so that the adapter for the most recent ``aliased=True`` call takes precedence as was the case in 1.2 and earlier. This broke the "elementtree" examples among other things. .. change:: :tags: bug, orm, py3k :tickets: 4674 Replaced the Python compatbility routines for ``getfullargspec()`` with a fully vendored version from Python 3.3. Originally, Python was emitting deprecation warnings for this function in Python 3.8 alphas. While this change was reverted, it was observed that Python 3 implementations for ``getfullargspec()`` are an order of magnitude slower as of the 3.4 series where it was rewritten against ``Signature``. While Python plans to improve upon this situation, SQLAlchemy projects for now are using a simple replacement to avoid any future issues. .. change:: :tags: bug, orm :tickets: 4694 Reworked the attribute mechanics used by :class:`.AliasedClass` to no longer rely upon calling ``__getattribute__`` on the MRO of the wrapped class, and to instead resolve the attribute normally on the wrapped class using getattr(), and then unwrap/adapt that. This allows a greater range of attribute styles on the mapped class including special ``__getattr__()`` schemes; but it also makes the code simpler and more resilient in general. .. change:: :tags: usecase, postgresql :tickets: 4717 Added support for column sorting flags when reflecting indexes for PostgreSQL, including ASC, DESC, NULLSFIRST, NULLSLAST. Also adds this facility to the reflection system in general which can be applied to other dialects in future releases. Pull request courtesy Eli Collins. .. change:: :tags: bug, postgresql :tickets: 4701 Fixed bug where PostgreSQL dialect could not correctly reflect an ENUM datatype that has no members, returning a list with ``None`` for the ``get_enums()`` call and raising a TypeError when reflecting a column which has such a datatype. The inspection now returns an empty list. .. change:: :tags: bug, sql :tickets: 4730 Fixed a series of quoting issues which all stemmed from the concept of the :func:`.literal_column` construct, which when being "proxied" through a subquery to be referred towards by a label that matches its text, the label would not have quoting rules applied to it, even if the string in the :class:`.Label` were set up as a :class:`.quoted_name` construct. Not applying quoting to the text of the :class:`.Label` is a bug because this text is strictly a SQL identifier name and not a SQL expression, and the string should not have quotes embedded into it already unlike the :func:`.literal_column` which it may be applied towards. The existing behavior of a non-labeled :func:`.literal_column` being propagated as is on the outside of a subquery is maintained in order to help with manual quoting schemes, although it's not clear if valid SQL can be generated for such a construct in any case. .. changelog:: ``` ### 1.3.4 ``` :released: May 27, 2019 .. change:: :tags: feature, mssql :tickets: 4657 Added support for SQL Server filtered indexes, via the ``mssql_where`` parameter which works similarly to that of the ``postgresql_where`` index function in the PostgreSQL dialect. .. seealso:: :ref:`mssql_index_where` .. change:: :tags: bug, misc :tickets: 4625 Removed errant "sqla_nose.py" symbol from MANIFEST.in which created an undesirable warning message. .. change:: :tags: bug, sql :tickets: 4653 Fixed that the :class:`.GenericFunction` class was inadvertently registering itself as one of the named functions. Pull request courtesy Adrien Berchet. .. change:: :tags: bug, engine, postgresql :tickets: 4663 Moved the "rollback" which occurs during dialect initialization so that it occurs after additional dialect-specific initialize steps, in particular those of the psycopg2 dialect which would inadvertently leave transactional state on the first new connection, which could interfere with some psycopg2-specific APIs which require that no transaction is started. Pull request courtesy Matthew Wilkes. .. change:: :tags: bug, orm :tickets: 4695 Fixed issue where the :paramref:`.AttributeEvents.active_history` flag would not be set for an event listener that propgated to a subclass via the :paramref:`.AttributeEvents.propagate` flag. This bug has been present for the full span of the :class:`.AttributeEvents` system. .. change:: :tags: bug, orm :tickets: 4690 Fixed regression where new association proxy system was still not proxying hybrid attributes when they made use of the ``hybrid_property.expression`` decorator to return an alternate SQL expression, or when the hybrid returned an arbitrary :class:`.PropComparator`, at the expression level. This involved futher generalization of the heuristics used to detect the type of object being proxied at the level of :class:`.QueryableAttribute`, to better detect if the descriptor ultimately serves mapped classes or column expressions. .. change:: :tags: bug, orm :tickets: 4686 Applied the mapper "configure mutex" against the declarative class mapping process, to guard against the race which can occur if mappers are used while dynamic module import schemes are still in the process of configuring mappers for related classes. This does not guard against all possible race conditions, such as if the concurrent import has not yet encountered the dependent classes as of yet, however it guards against as much as possible within the SQLAlchemy declarative process. .. change:: :tags: bug, mssql :tickets: 4680 Added error code 20047 to "is_disconnect" for pymssql. Pull request courtesy Jon Schuff. .. change:: :tags: bug, postgresql, orm :tickets: 4661 Fixed an issue where the "number of rows matched" warning would emit even if the dialect reported "supports_sane_multi_rowcount=False", as is the case for psycogp2 with ``use_batch_mode=True`` and others. .. change:: :tags: bug, sql :tickets: 4618 Fixed issue where double negation of a boolean column wouldn't reset the "NOT" operator. .. change:: :tags: mysql, bug :tickets: 4650 Added support for DROP CHECK constraint which is required by MySQL 8.0.16 to drop a CHECK constraint; MariaDB supports plain DROP CONSTRAINT. The logic distinguishes between the two syntaxes by checking the server version string for MariaDB presence. Alembic migrations has already worked around this issue by implementing its own DROP for MySQL / MariaDB CHECK constraints, however this change implements it straight in Core so that its available for general use. Pull request courtesy Hannes Hansen. .. change:: :tags: bug, orm :tickets: 4647 A warning is now emitted for the case where a transient object is being merged into the session with :meth:`.Session.merge` when that object is already transient in the :class:`.Session`. This warns for the case where the object would normally be double-inserted. .. change:: :tags: bug, orm :tickets: 4676 Fixed regression in new relationship m2o comparison logic first introduced at :ref:`change_4359` when comparing to an attribute that is persisted as NULL and is in an un-fetched state in the mapped instance. Since the attribute has no explicit default, it needs to default to NULL when accessed in a persistent setting. .. change:: :tags: bug, sql :tickets: 4569 The :class:`.GenericFunction` namespace is being migrated so that function names are looked up in a case-insensitive manner, as SQL functions do not collide on case sensitive differences nor is this something which would occur with user-defined functions or stored procedures. Lookups for functions declared with :class:`.GenericFunction` now use a case insensitive scheme, however a deprecation case is supported which allows two or more :class:`.GenericFunction` objects with the same name of different cases to exist, which will cause case sensitive lookups to occur for that particular name, while emitting a warning at function registration time. Thanks to Adrien Berchet for a lot of work on this complicated feature. .. changelog:: ``` ### 1.3.3 ``` :released: April 15, 2019 .. change:: :tags: bug, postgresql :tickets: 4601 Fixed regression from release 1.3.2 caused by :ticket:`4562` where a URL that contained only a query string and no hostname, such as for the purposes of specifying a service file with connection information, would no longer be propagated to psycopg2 properly. The change in :ticket:`4562` has been adjusted to further suit psycopg2's exact requirements, which is that if there are any connection parameters whatsoever, the "dsn" parameter is no longer required, so in this case the query string parameters are passed alone. .. change:: :tags: bug, pool :tickets: 4585 Fixed behavioral regression as a result of deprecating the "use_threadlocal" flag for :class:`.Pool`, where the :class:`.SingletonThreadPool` no longer makes use of this option which causes the "rollback on return" logic to take place when the same :class:`.Engine` is used multiple times in the context of a transaction to connect or implicitly execute, thereby cancelling the transaction. While this is not the recommended way to work with engines and connections, it is nonetheless a confusing behavioral change as when using :class:`.SingletonThreadPool`, the transaction should stay open regardless of what else is done with the same engine in the same thread. The ``use_threadlocal`` flag remains deprecated however the :class:`.SingletonThreadPool` now implements its own version of the same logic. .. change:: :tags: bug, orm :tickets: 4584 Fixed 1.3 regression in new "ambiguous FROMs" query logic introduced in :ref:`change_4365` where a :class:`.Query` that explicitly places an entity in the FROM clause with :meth:`.Query.select_from` and also joins to it using :meth:`.Query.join` would later cause an "ambiguous FROM" error if that entity were used in additional joins, as the entity appears twice in the "from" list of the :class:`.Query`. The fix resolves this ambiguity by folding the standalone entity into the join that it's already a part of in the same way that ultimately happens when the SELECT statement is rendered. .. change:: :tags: bug, ext :tickets: 4603 Fixed bug where using ``copy.copy()`` or ``copy.deepcopy()`` on :class:`.MutableList` would cause the items within the list to be duplicated, due to an inconsistency in how Python pickle and copy both make use of ``__getstate__()`` and ``__setstate__()`` regarding lists. In order to resolve, a ``__reduce_ex__`` method had to be added to :class:`.MutableList`. In order to maintain backwards compatibility with existing pickles based on ``__getstate__()``, the ``__setstate__()`` method remains as well; the test suite asserts that pickles made against the old version of the class can still be deserialized by the pickle module. .. change:: :tags: bug, orm :tickets: 4606 Adjusted the :meth:`.Query.filter_by` method to not call :func:`.and()` internally against multiple criteria, instead passing it off to :meth:`.Query.filter` as a series of criteria, instead of a single criteria. This allows :meth:`.Query.filter_by` to defer to :meth:`.Query.filter`'s treatment of variable numbers of clauses, including the case where the list is empty. In this case, the :class:`.Query` object will not have a ``.whereclause``, which allows subsequent "no whereclause" methods like :meth:`.Query.select_from` to behave consistently. .. change:: :tags: bug, mssql :tickets: 4587 Fixed issue in SQL Server dialect where if a bound parameter were present in an ORDER BY expression that would ultimately not be rendered in the SQL Server version of the statement, the parameters would still be part of the execution parameters, leading to DBAPI-level errors. Pull request courtesy Matt Lewellyn. .. changelog:: ``` ### 1.3.2 ``` :released: April 2, 2019 .. change:: :tags: bug, documentation, sql :tickets: 4580 Thanks to :ref:`change_3981`, we no longer need to rely on recipes that subclass dialect-specific types directly, :class:`.TypeDecorator` can now handle all cases. Additionally, the above change made it slightly less likely that a direct subclass of a base SQLAlchemy type would work as expected, which could be misleading. Documentation has been updated to use :class:`.TypeDecorator` for these examples including the PostgreSQL "ArrayOfEnum" example datatype and direct support for the "subclass a type directly" has been removed. .. change:: :tags: bug, postgresql :tickets: 4550 Modified the :paramref:`.Select.with_for_update.of` parameter so that if a join or other composed selectable is passed, the individual :class:`.Table` objects will be filtered from it, allowing one to pass a join() object to the parameter, as occurs normally when using joined table inheritance with the ORM. Pull request courtesy Raymond Lu. .. change:: :tags: feature, postgresql :tickets: 4562 Added support for parameter-less connection URLs for the psycopg2 dialect, meaning, the URL can be passed to :func:`.create_engine` as ``"postgresql+psycopg2://"`` with no additional arguments to indicate an empty DSN passed to libpq, which indicates to connect to "localhost" with no username, password, or database given. Pull request courtesy Julian Mehnle. .. change:: :tags: bug, orm, ext :tickets: 4574, 4573 Restored instance-level support for plain Python descriptors, e.g. ``property`` objects, in conjunction with association proxies, in that if the proxied object is not within ORM scope at all, it gets classified as "ambiguous" but is proxed directly. For class level access, a basic class level``__get__()`` now returns the :class:`.AmbiguousAssociationProxyInstance` directly, rather than raising its exception, which is the closest approximation to the previous behavior that returned the :class:`.AssociationProxy` itself that's possible. Also improved the stringification of these objects to be more descriptive of current state. .. change:: :tags: bug, orm :tickets: 4537 Fixed bug where use of :func:`.with_polymorphic` or other aliased construct would not properly adapt when the aliased target were used as the :meth:`.Select.correlate_except` target of a subquery used inside of a :func:`.column_property`. This required a fix to the clause adaption mechanics to properly handle a selectable that shows up in the "correlate except" list, in a similar manner as which occurs for selectables that show up in the "correlate" list. This is ultimately a fairly fundamental bug that has lasted for a long time but it is hard to come across it. .. change:: :tags: bug, orm :tickets: 4566 Fixed regression where a new error message that was supposed to raise when attempting to link a relationship option to an AliasedClass without using :meth:`.PropComparator.of_type` would instead raise an ``AttributeError``. Note that in 1.3, it is no longer valid to create an option path from a plain mapper relationship to an :class:`.AliasedClass` without using :meth:`.PropComparator.of_type`. .. changelog:: ```Links
- PyPI: https://pypi.org/project/sqlalchemy - Changelog: https://pyup.io/changelogs/sqlalchemy/ - Homepage: http://www.sqlalchemy.orgUpdate tqdm from 4.31.1 to 4.32.2.
Changelog
### 4.32.1 ``` - fix `notebook` with unknown `total` (743) ``` ### 4.32.0 ``` - support `unit_scale` in `notebook` - support negative update (432, 545) - add `reset()` function (547, 545) - add `[python setup.py] make run` - add and update documentation - example of dynamic usage (735, 545, 547, 432, 374) - note writing issues (737) - update badges - add [PyData2019 slides link](https://tqdm.github.io/PyData2019/slides.html) - add [JOSS paper](https://github.com/openjournals/joss-papers/blob/joss.01277/joss.01277/10.21105.joss.01277.pdf) - update manpages - add docker install - add snapcraft install - notebooks: add binder, rename RMOTR => notebooks.ai (679) - prettify and unify contributors/maintainers/authors - CI and release framework updates - add snapcraft snaps (647) - add travis auto-deployment (685) + PyPI releases + docker devel/releases - update deployment dev docs - fix travis deploy pymake - update .gitinore - add & update unit tests - automate more documentation ```Links
- PyPI: https://pypi.org/project/tqdm - Changelog: https://pyup.io/changelogs/tqdm/ - Repo: https://github.com/tqdm/tqdmUpdate pyyaml from 5.1 to 5.1.1.
The bot wasn't able to find a changelog for this release. Got an idea?
Links
- PyPI: https://pypi.org/project/pyyaml - Repo: https://github.com/yaml/pyyamlUpdate hypothesis from 4.14.2 to 4.24.6.
The bot wasn't able to find a changelog for this release. Got an idea?
Links
- PyPI: https://pypi.org/project/hypothesis - Repo: https://github.com/HypothesisWorks/hypothesis/tree/master/hypothesis-pythonUpdate pytest from 4.4.0 to 5.0.0.
Changelog
### 5.0.0 ``` ========================= Important --------- This release is a Python3.5+ only release. For more details, see our `Python 2.7 and 3.4 support plan <https://docs.pytest.org/en/latest/py27-py34-deprecation.html>`__. Removals -------- - `1149 <https://github.com/pytest-dev/pytest/issues/1149>`_: Pytest no longer accepts prefixes of command-line arguments, for example typing ``pytest --doctest-mod`` inplace of ``--doctest-modules``. This was previously allowed where the ``ArgumentParser`` thought it was unambiguous, but this could be incorrect