Changelog
### 3.2.3
```
==================
Other Changes and Additions
---------------------------
- Updated IERS A URLs due to USNO prolonged maintenance. [9443]
```
### 3.2.2
```
==================
Bug fixes
---------
astropy.convolution
^^^^^^^^^^^^^^^^^^^
- Fixed a bug in ``discretize_oversample_1D/2D()`` from
``astropy.convolution.utils``, which might occasionally introduce unexpected
oversampling grid dimensions due to a numerical precision issue. [9293]
- Fixed a bug [9168] where having a kernel defined using unitless astropy
quantity objects would result in a crash [9300]
astropy.coordinates
^^^^^^^^^^^^^^^^^^^
- Fix concatenation of representations for cases where the units were different.
[8877]
- Check for NaN values in catalog and match coordinates before building and
querying the ``KDTree`` for coordinate matching. [9007]
- Fix sky coordinate matching when a dimensionless distance is provided. [9008]
- Raise a faster and more meaningful error message when differential data units
are not compatible with a containing representation's units. [9064]
- Changed the timescale in ICRS to CIRS from 'tdb' to 'tt' conversion and
vice-versa, as the erfa function that gets called in the process, pnm06a
accepts time in TT. [9079]
astropy.io.ascii
^^^^^^^^^^^^^^^^
- Fixed the fast reader when used in parallel and with the multiprocessing
'spawn' method (which is the default on MacOS X with Python 3.8 and later),
and enable parallel fast reader on Windows. [8853]
astropy.io.fits
^^^^^^^^^^^^^^^
- Fixes bug where an invalid TRPOS<n> keyword was being generated for FITS
time column when no location was available. [8784]
- Fixed a wrong exception when converting a Table with a unit that is not FITS
compliant and not convertible to a string using ``format='fits'``. [8906]
- Fixed an issue with A3DTABLE extension that could not be read. [9012]
- Fixed the update of the header when creating GroupsHDU from data. [9216]
astropy.nddata
^^^^^^^^^^^^^^
- Fix to ``add_array``, which now accepts ``array_small`` having dimensions
equal to ``array_large``, instead of only allowing smaller sizes of
arrays. [9118]
astropy.stats
^^^^^^^^^^^^^
- Fixed ``median_absolute_deviation`` for the case where ``ignore_nan=True``
and an input masked array contained both NaNs and infs. [9307]
astropy.table
^^^^^^^^^^^^^
- Comparisons between ``Column`` instances and ``Quantity`` will now
correctly take into account the unit (as was already the case for
regular operations such as addition). [8904]
astropy.time
^^^^^^^^^^^^
- Allow ``Time`` to be initialized with an empty value for all formats. [8854]
- Fixed a troubling bug in which ``Time`` could loose precision, with deviations
of 300 ns. [9328]
astropy.timeseries
^^^^^^^^^^^^^^^^^^
- Fixed handling of ``Quantity`` input data for all methods of
``LombScarge.false_alarm_probabilty``. [9246]
astropy.units
^^^^^^^^^^^^^
- Allow conversion of ``Column`` with logarithmic units to a suitable
``Quantity`` subclass if ``subok=True``. [9188]
- Ensured that we simplify powers to smaller denominators if that is
consistent within rounding precision. [9267]
- Ensured that the powers shown in a unit's repr are always correct,
not oversimplified. [9267]
astropy.utils
^^^^^^^^^^^^^
- Fixed ``find_api_page`` access by using custom request headers and HTTPS
when version is specified. [9032]
- Make ``download_file`` (and by extension ``get_readable_fileobj`` and others)
check the size of downloaded files against the size claimed by the server.
[9302]
- Fix ``find_current_module`` so that it works properly if astropy is being used
inside a bundle such as that produced by PyInstaller. [8845]
- Fix path to renamed classes, which previously included duplicate path/module
information under certain circumstances. [8845]
astropy.visualization
^^^^^^^^^^^^^^^^^^^^^
- Silence numpy runtime warnings in ``WCSAxes`` when drawing grids. [8882]
astropy.wcs
^^^^^^^^^^^
- Fixed equality test between ``cunit`` where the first element was equal but
the following elements differed. [9154]
- Fixed a crash while loading a WCS from headers containing duplicate SIP
keywords. [8893]
- Fixed a possible buffer overflow when using too large negative indices for
``cunit`` or ``ctype`` [9151]
- Fixed reference counting in ``WCSBase.__init__`` [9166]
- Fix ``SlicedLowLevelWCS`` ``world_to_pixel_values`` and
``pixel_to_world_values`` when inputs need broadcasting to the same shape.
(i.e. when one input is sliced out) [9250]
- Fixed a bug that caused ``WCS.array_shape``, ``WCS.pixel_shape`` and
``WCS.pixel_bounds`` to be incorrect after using ``WCS.sub``. [9095]
Other Changes and Additions
---------------------------
- Fixed a bug that caused files outside of the astropy module directory to be
included as package data, resulting in some cases in errors when doing
repeated builds. [9039]
```
Links
- PyPI: https://pypi.org/project/astropy
- Changelog: https://pyup.io/changelogs/astropy/
- Homepage: http://astropy.org
Changelog
### 0.14.0
```
--------------
- Improved the load balancing between workers to avoid stranglers caused by an
excessively large batch size when the task duration is varying significantly
(because of the combined use of ``joblib.Parallel`` and ``joblib.Memory``
with a partially warmed cache for instance).
https://github.com/joblib/joblib/pull/899
- Add official support for Python 3.8: fixed protocol number in `Hasher`
and updated tests.
- Fix a deadlock when using the dask backend (when scattering large numpy
arrays).
https://github.com/joblib/joblib/pull/914
- Warn users that they should never use `joblib.load` with files from
untrusted sources. Fix security related API change introduced in numpy
1.6.3 that would prevent using joblib with recent numpy versions.
https://github.com/joblib/joblib/pull/879
- Upgrade to cloudpickle 1.1.1 that add supports for the upcoming
Python 3.8 release among other things.
https://github.com/joblib/joblib/pull/878
- Fix semaphore availability checker to avoid spawning resource trackers
on module import.
https://github.com/joblib/joblib/pull/893
- Fix the oversubscription protection to only protect against nested
`Parallel` calls. This allows `joblib` to be run in background threads.
https://github.com/joblib/joblib/pull/934
- Fix `ValueError` (negative dimensions) when pickling large numpy arrays on
Windows.
https://github.com/joblib/joblib/pull/920
- Upgrade to loky 2.6.0 that add supports for the setting environment variables
in child before loading any module.
https://github.com/joblib/joblib/pull/940
- Fix the oversubscription protection for native libraries using threadpools
(OpenBLAS, MKL, Blis and OpenMP runtimes).
The maximal number of threads is can now be set in children using the
``inner_max_num_threads`` in ``parallel_backend``. It defaults to
``cpu_count() // n_jobs``.
https://github.com/joblib/joblib/pull/940
```
Links
- PyPI: https://pypi.org/project/joblib
- Changelog: https://pyup.io/changelogs/joblib/
- Docs: https://joblib.readthedocs.io
Changelog
### 0.46.0
```
--------------
This release significantly reworked one of the main parts of Numba, the compiler
pipeline, to make it more extensible and easier to use. The purpose of this was
to continue enhancing Numba's ability for use as a compiler toolkit. In a
similar vein, Numba now has an extension registration mechanism to allow other
Numba-using projects to automatically have their Numba JIT compilable functions
discovered. There were also a number of other related compiler toolkit
enhancement added along with some more NumPy features and a lot of bug fixes.
This release has updated the CUDA Array Interface specification to version 2,
which clarifies the `strides` attribute for C-contiguous arrays and specifies
the treatment for zero-size arrays. The implementation in Numba has been
changed and may affect downstream packages relying on the old behavior
(see issue 4661).
Enhancements from user contributed PRs (with thanks!):
* Aaron Meurer fixed some Python issues in the code base in 4345 and 4341.
* Ashwin Srinath fixed a CUDA performance bug via 4576.
* Ethan Pronovost added support for triangular indices functions in 4601 (the
NumPy functions ``tril_indices``, ``tril_indices_from``, ``triu_indices``, and
``triu_indices_from``).
* Gerald Dalley fixed a tear down race occurring in Python 2.
* Gregory R. Lee fixed the use of deprecated ``inspect.getargspec``.
* Guilherme Leobas contributed five PRs, adding support for ``np.append`` and
``np.count_nonzero`` in 4518 and 4386. The typed List was fixed to accept
unsigned integers in 4510. 4463 made a fix to NamedTuple internals and 4397
updated the docs for ``np.sum``.
* James Bourbeau added a new feature to permit the automatic application of the
`jit` decorator to a whole module in 4331. Also some small fixes to the docs
and the code base were made in 4447 and 4433, and a fix to inplace array
operation in 4228.
* Jim Crist fixed a bug in the rendering of patched errors in 4464.
* Leo Fang updated the CUDA Array Interface contract in 4609.
* Pearu Peterson added support for Unicode based NumPy arrays in 4425.
* Peter Andreas Entschev fixed a CUDA concurrency bug in 4581.
* Lucio Fernandez-Arjona extended Numba's ``np.sum`` support to now accept the
``dtype`` kwarg in 4472.
* Pedro A. Morales Maries added support for ``np.cross`` in 4128 and also added
the necessary extension ``numba.numpy_extensions.cross2d`` in 4595.
* David Hoese, Eric Firing, Joshua Adelman, and Juan Nunez-Iglesias all made
documentation fixes in 4565, 4482, 4455, 4375 respectively.
* Vyacheslav Smirnov and Rujal Desai enabled support for ``count()`` on unicode
strings in 4606.
General Enhancements:
* PR 4113: Add rewrite for semantic constants.
* PR 4128: Add np.cross support
* PR 4162: Make IR comparable and legalize it.
* PR 4208: R&D inlining, jitted and overloaded.
* PR 4331: Automatic JIT of called functions
* PR 4353: Inspection tool to check what numba supports
* PR 4386: Implement np.count_nonzero
* PR 4425: Unicode array support
* PR 4427: Entrypoints for numba extensions
* PR 4467: Literal dispatch
* PR 4472: Allow dtype input argument in np.sum
* PR 4513: New compiler.
* PR 4518: add support for np.append
* PR 4554: Refactor NRT C-API
* PR 4556: 0.46 scheduled deprecations
* PR 4567: Add env var to disable performance warnings.
* PR 4568: add np.array_equal support
* PR 4595: Implement numba.cross2d
* PR 4601: Add triangular indices functions
* PR 4606: Enable support for count() method for unicode string
Fixes:
* PR 4228: Fix inplace operator error for arrays
* PR 4282: Detect and raise unsupported on generator expressions
* PR 4305: Don't allow the allocation of mutable objects written into a
container to be hoisted.
* PR 4311: Avoid deprecated use of inspect.getargspec
* PR 4328: Replace GC macro with function call
* PR 4330: Loosen up typed container casting checks
* PR 4341: Fix some coding lines at the top of some files (utf8 -> utf-8)
* PR 4345: Replace "import \*" with explicit imports in numba/types
* PR 4346: Fix incorrect alg in isupper for ascii strings.
* PR 4349: test using jitclass in typed-list
* PR 4361: Add allocation hoisting info to LICM section at diagnostic L4
* PR 4366: Offset search box to avoid wrapping on some pages with Safari.
Fixes 4365.
* PR 4372: Replace all "except BaseException" with "except Exception".
* PR 4407: Restore the "free" conda channel for NumPy 1.10 support.
* PR 4408: Add lowering for constant bytes.
* PR 4409: Add exception chaining for better error context
* PR 4411: Name of type should not contain user facing description for debug.
* PR 4412: Fix 4387. Limit the number of return types for recursive functions
* PR 4426: Fixed two module teardown races in py2.
* PR 4431: Fix and test numpy.random.random_sample(n) for np117
* PR 4463: NamedTuple - Raises an error on non-iterable elements
* PR 4464: Add a newline in patched errors
* PR 4474: Fix liveness for remove dead of parfors (and other IR extensions)
* PR 4510: Make List.__getitem__ accept unsigned parameters
* PR 4512: Raise specific error at typing time for iteration on >1D array.
* PR 4532: Fix static_getitem with Literal type as index
* PR 4547: Update to inliner cost model information.
* PR 4557: Use specific random number seed when generating arbitrary test data
* PR 4559: Adjust test timeouts
* PR 4564: Skip unicode array tests on ppc64le that trigger an LLVM bug
* PR 4621: Fix packaging issue due to missing numba/cext
* PR 4623: Fix issue 4520 due to storage model mismatch
* PR 4644: Updates for llvmlite 0.30.0
CUDA Enhancements/Fixes:
* PR 4410: Fix 4111. cudasim mishandling recarray
* PR 4576: Replace use of `np.prod` with `functools.reduce` for computing size
from shape
* PR 4581: Prevent taking the GIL in ForAll
* PR 4592: Fix 4589. Just pass NULL for b2d_func for constant dynamic
sharedmem
* PR 4609: Update CUDA Array Interface & Enforce Numba compliance
* PR 4619: Implement math.{degrees, radians} for the CUDA target.
* PR 4675: Bump cuda array interface to version 2
Documentation Updates:
* PR 4317: Add docs for ARMv8/AArch64
* PR 4318: Add supported platforms to the docs. Closes 4316
* PR 4375: Add docstrings to inspect methods
* PR 4388: Update Python 2.7 EOL statement
* PR 4397: Add note about np.sum
* PR 4447: Minor parallel performance tips edits
* PR 4455: Clarify docs for typed dict with regard to arrays
* PR 4482: Fix example in guvectorize docstring.
* PR 4541: fix two typos in architecture.rst
* PR 4548: Document numba.extending.intrinsic and inlining.
* PR 4565: Fix typo in jit-compilation docs
* PR 4607: add dependency list to docs
* PR 4614: Add documentation for implementing new compiler passes.
CI Updates:
* PR 4415: Make 32bit incremental builds on linux not use free channel
* PR 4433: Removes stale azure comment
* PR 4493: Fix Overload Inliner wrt CUDA Intrinsics
* PR 4593: Enable Azure CI batching
Contributors:
* Aaron Meurer
* Ashwin Srinath
* David Hoese
* Ehsan Totoni (core dev)
* Eric Firing
* Ethan Pronovost
* Gerald Dalley
* Gregory R. Lee
* Guilherme Leobas
* James Bourbeau
* Jim Crist
* Joshua Adelman
* Juan Nunez-Iglesias
* Leo Fang
* Lucio Fernandez-Arjona
* Pearu Peterson
* Pedro A. Morales Marie
* Peter Andreas Entschev
* Rujal Desai
* Siu Kwan Lam (core dev)
* Stan Seibert (core dev)
* Stuart Archibald (core dev)
* Todd A. Anderson (core dev)
* Valentin Haenel (core dev)
* Vyacheslav Smirnov
```
### 0.45.1
```
--------------
This patch release addresses some regressions reported in the 0.45.0 release and
```
Links
- PyPI: https://pypi.org/project/numba
- Changelog: https://pyup.io/changelogs/numba/
- Repo: http://numba.github.com
Changelog
### 1.3.10
```
:include_notes_from: unreleased_13
.. changelog::
```
### 1.3.9
```
:released: October 4, 2019
.. change::
:tags: usecase, engine
:tickets: 4857
Added new :func:`.create_engine` parameter
:paramref:`.create_engine.max_identifier_length`. This overrides the
dialect-coded "max identifier length" in order to accommodate for databases
that have recently changed this length and the SQLAlchemy dialect has
not yet been adjusted to detect for that version. This parameter interacts
with the existing :paramref:`.create_engine.label_length` parameter in that
it establishes the maximum (and default) value for anonymously generated
labels. Additionally, post-connection detection of max identifier lengths
has been added to the dialect system. This feature is first being used
by the Oracle dialect.
.. seealso::
:ref:`oracle_max_identifier_lengths` - in the Oracle dialect documentation
.. change::
:tags: usecase, oracle
:tickets: 4857
The Oracle dialect now emits a warning if Oracle version 12.2 or greater is
used, and the :paramref:`.create_engine.max_identifier_length` parameter is
not set. The version in this specific case defaults to that of the
"compatibility" version set in the Oracle server configuration, not the
actual server version. In version 1.4, the default max_identifier_length
for 12.2 or greater will move to 128 characters. In order to maintain
forwards compatibility, applications should set
:paramref:`.create_engine.max_identifier_length` to 30 in order to maintain
the same length behavior, or to 128 in order to test the upcoming behavior.
This length determines among other things how generated constraint names
are truncated for statements like ``CREATE CONSTRAINT`` and ``DROP
CONSTRAINT``, which means a the new length may produce a name-mismatch
against a name that was generated with the old length, impacting database
migrations.
.. seealso::
:ref:`oracle_max_identifier_lengths` - in the Oracle dialect documentation
.. change::
:tags: usecase, sqlite
:tickets: 4863
Added support for sqlite "URI" connections, which allow for sqlite-specific
flags to be passed in the query string such as "read only" for Python
sqlite3 drivers that support this.
.. seealso::
:ref:`pysqlite_uri_connections`
.. change::
:tags: bug, tests
:tickets: 4285
Fixed unit test regression released in 1.3.8 that would cause failure for
Oracle, SQL Server and other non-native ENUM platforms due to new
enumeration tests added as part of :ticket:`4285` enum sortability in the
unit of work; the enumerations created constraints that were duplicated on
name.
.. change::
:tags: bug, oracle
:tickets: 4886
Restored adding cx_Oracle.DATETIME to the setinputsizes() call when a
SQLAlchemy :class:`.Date`, :class:`.DateTime` or :class:`.Time` datatype is
used, as some complex queries require this to be present. This was removed
in the 1.2 series for arbitrary reasons.
.. change::
:tags: bug, mssql
:tickets: 4883
Added identifier quoting to the schema name applied to the "use" statement
which is invoked when a SQL Server multipart schema name is used within a
:class:`.Table` that is being reflected, as well as for :class:`.Inspector`
methods such as :meth:`.Inspector.get_table_names`; this accommodates for
special characters or spaces in the database name. Additionally, the "use"
statement is not emitted if the current database matches the target owner
database name being passed.
.. change::
:tags: bug, orm
:tickets: 4872
Fixed regression in selectinload loader strategy caused by :ticket:`4775`
(released in version 1.3.6) where a many-to-one attribute of None would no
longer be populated by the loader. While this was usually not noticeable
due to the lazyloader populating None upon get, it would lead to a detached
instance error if the object were detached.
.. change::
:tags: bug, orm
:tickets: 4873
Passing a plain string expression to :meth:`.Session.query` is deprecated,
as all string coercions were removed in :ticket:`4481` and this one should
have been included. The :func:`.literal_column` function may be used to
produce a textual column expression.
.. change::
:tags: usecase, sql
:tickets: 4847
Added an explicit error message for the case when objects passed to
:class:`.Table` are not :class:`.SchemaItem` objects, rather than resolving
to an attribute error.
.. change::
:tags: bug, orm
:tickets: 4890
A warning is emitted for a condition in which the :class:`.Session` may
implicitly swap an object out of the identity map for another one with the
same primary key, detaching the old one, which can be an observed result of
load operations which occur within the :meth:`.SessionEvents.after_flush`
hook. The warning is intended to notify the user that some special
condition has caused this to happen and that the previous object may not be
in the expected state.
.. change::
:tags: bug, sql
:tickets: 4837
Characters that interfere with "pyformat" or "named" formats in bound
parameters, namely ``%, (, )`` and the space character, as well as a few
other typically undesirable characters, are stripped early for a
:func:`.bindparam` that is using an anonymized name, which is typically
generated automatically from a named column which itself includes these
characters in its name and does not use a ``.key``, so that they do not
interfere either with the SQLAlchemy compiler's use of string formatting or
with the driver-level parsing of the parameter, both of which could be
demonstrated before the fix. The change only applies to anonymized
parameter names that are generated and consumed internally, not end-user
defined names, so the change should have no impact on any existing code.
Applies in particular to the psycopg2 driver which does not otherwise quote
special parameter names, but also strips leading underscores to suit Oracle
(but not yet leading numbers, as some anon parameters are currently
entirely numeric/underscore based); Oracle in any case continues to quote
parameter names that include special characters.
.. changelog::
```
### 1.3.8
```
:released: August 27, 2019
.. change::
:tags: bug, orm
:tickets: 4823
Fixed bug where :class:`.Load` objects were not pickleable due to
mapper/relationship state in the internal context dictionary. These
objects are now converted to picklable using similar techniques as that of
other elements within the loader option system that have long been
serializable.
.. change::
:tags: bug, postgresql
:tickets: 4623
Revised the approach for the just added support for the psycopg2
"execute_values()" feature added in 1.3.7 for :ticket:`4623`. The approach
relied upon a regular expression that would fail to match for a more
complex INSERT statement such as one which had subqueries involved. The
new approach matches exactly the string that was rendered as the VALUES
clause.
.. change::
:tags: usecase, orm
:tickets: 4285
Added support for the use of an :class:`.Enum` datatype using Python
pep-435 enumeration objects as values for use as a primary key column
mapped by the ORM. As these values are not inherently sortable, as
required by the ORM for primary keys, a new
:attr:`.TypeEngine.sort_key_function` attribute is added to the typing
system which allows any SQL type to implement a sorting for Python objects
of its type which is consulted by the unit of work. The :class:`.Enum`
type then defines this using the database value of a given enumeration.
The sorting scheme can be also be redefined by passing a callable to the
:paramref:`.Enum.sort_key_function` parameter. Pull request courtesy
Nicolas Caniart.
.. change::
:tags: bug, engine
:tickets: 4807
Fixed an issue whereby if the dialect "initialize" process which occurs on
first connect would encounter an unexpected exception, the initialize
process would fail to complete and then no longer attempt on subsequent
connection attempts, leaving the dialect in an un-initialized, or partially
initialized state, within the scope of parameters that need to be
established based on inspection of a live connection. The "invoke once"
logic in the event system has been reworked to accommodate for this
occurrence using new, private API features that establish an "exec once"
hook that will continue to allow the initializer to fire off on subsequent
connections, until it completes without raising an exception. This does not
impact the behavior of the existing ``once=True`` flag within the event
system.
.. change::
:tags: bug, sqlite, reflection
:tickets: 4810
Fixed bug where a FOREIGN KEY that was set up to refer to the parent table
by table name only without the column names would not correctly be
reflected as far as setting up the "referred columns", since SQLite's
PRAGMA does not report on these columns if they weren't given explicitly.
For some reason this was harcoded to assume the name of the local column,
which might work for some cases but is not correct. The new approach
reflects the primary key of the referred table and uses the constraint
columns list as the referred columns list, if the remote column(s) aren't
present in the reflected pragma directly.
.. change::
:tags: bug, postgresql
:tickets: 4822
Fixed bug where Postgresql operators such as
:meth:`.postgresql.ARRAY.Comparator.contains` and
:meth:`.postgresql.ARRAY.Comparator.contained_by` would fail to function
correctly for non-integer values when used against a
:class:`.postgresql.array` object, due to an erroneous assert statement.
.. change::
:tags: feature, engine
:tickets: 4815
Added new parameter :paramref:`.create_engine.hide_parameters` which when
set to True will cause SQL parameters to no longer be logged, nor rendered
in the string representation of a :class:`.StatementError` object.
.. change::
:tags: usecase, postgresql
:tickets: 4824
Added support for reflection of CHECK constraints that include the special
PostgreSQL qualifier "NOT VALID", which can be present for CHECK
constraints that were added to an exsiting table with the directive that
they not be applied to existing data in the table. The PostgreSQL
dictionary for CHECK constraints as returned by
:meth:`.Inspector.get_check_constraints` may include an additional entry
``dialect_options`` which within will contain an entry ``"not_valid":
True`` if this symbol is detected. Pull request courtesy Bill Finn.
.. changelog::
```
### 1.3.7
```
:released: August 14, 2019
.. change::
:tags: bug, sql
:tickets: 4778
Fixed issue where :class:`.Index` object which contained a mixture of
functional expressions which were not resolvable to a particular column,
in combination with string-based column names, would fail to initialize
its internal state correctly leading to failures during DDL compilation.
.. change::
:tags: bug, sqlite
:tickets: 4798
The dialects that support json are supposed to take arguments
``json_serializer`` and ``json_deserializer`` at the create_engine() level,
however the SQLite dialect calls them ``_json_serilizer`` and
``_json_deserilalizer``. The names have been corrected, the old names are
accepted with a change warning, and these parameters are now documented as
:paramref:`.create_engine.json_serializer` and
:paramref:`.create_engine.json_deserializer`.
.. change::
:tags: bug, mysql
:tickets: 4804
The MySQL dialects will emit "SET NAMES" at the start of a connection when
charset is given to the MySQL driver, to appease an apparent behavior
observed in MySQL 8.0 that raises a collation error when a UNION includes
string columns unioned against columns of the form CAST(NULL AS CHAR(..)),
which is what SQLAlchemy's polymorphic_union function does. The issue
seems to have affected PyMySQL for at least a year, however has recently
appeared as of mysqlclient 1.4.4 based on changes in how this DBAPI creates
a connection. As the presence of this directive impacts three separate
MySQL charset settings which each have intricate effects based on their
presense, SQLAlchemy will now emit the directive on new connections to
ensure correct behavior.
.. change::
:tags: usecase, postgresql
:tickets: 4623
Added new dialect flag for the psycopg2 dialect, ``executemany_mode`` which
supersedes the previous experimental ``use_batch_mode`` flag.
``executemany_mode`` supports both the "execute batch" and "execute values"
functions provided by psycopg2, the latter which is used for compiled
:func:`.insert` constructs. Pull request courtesy Yuval Dinari.
.. seealso::
:ref:`psycopg2_executemany_mode`
.. change::
:tags: bug, sql
:tickets: 4787
Fixed bug where :meth:`.TypeEngine.column_expression` method would not be
applied to subsequent SELECT statements inside of a UNION or other
:class:`.CompoundSelect`, even though the SELECT statements are rendered at
the topmost level of the statement. New logic now differentiates between
rendering the column expression, which is needed for all SELECTs in the
list, vs. gathering the returned data type for the result row, which is
needed only for the first SELECT.
.. change::
:tags: bug, sqlite
:tickets: 4793
Fixed bug where usage of "PRAGMA table_info" in SQLite dialect meant that
reflection features to detect for table existence, list of table columns,
and list of foreign keys, would default to any table in any attached
database, when no schema name was given and the table did not exist in the
base schema. The fix explicitly runs PRAGMA for the 'main' schema and then
the 'temp' schema if the 'main' returned no rows, to maintain the behavior
of tables + temp tables in the "no schema" namespace, attached tables only
in the "schema" namespace.
.. change::
:tags: bug, sql
:tickets: 4780
Fixed issue where internal cloning of SELECT constructs could lead to a key
error if the copy of the SELECT changed its state such that its list of
columns changed. This was observed to be occurring in some ORM scenarios
which may be unique to 1.3 and above, so is partially a regression fix.
.. change::
:tags: bug, orm
:tickets: 4777
Fixed regression caused by new selectinload for many-to-one logic where
a primaryjoin condition not based on real foreign keys would cause
KeyError if a related object did not exist for a given key value on the
parent object.
.. change::
:tags: usecase, mysql
:tickets: 4783
Added reserved words ARRAY and MEMBER to the MySQL reserved words list, as
MySQL 8.0 has now made these reserved.
.. change::
:tags: bug, events
:tickets: 4794
Fixed issue in event system where using the ``once=True`` flag with
dynamically generated listener functions would cause event registration of
future events to fail if those listener functions were garbage collected
after they were used, due to an assumption that a listened function is
strongly referenced. The "once" wrapped is now modified to strongly
reference the inner function persistently, and documentation is updated
that using "once" does not imply automatic de-registration of listener
functions.
.. change::
:tags: bug, mysql
:tickets: 4751
Added another fix for an upstream MySQL 8 issue where a case sensitive
table name is reported incorrectly in foreign key constraint reflection,
this is an extension of the fix first added for :ticket:`4344` which
affects a case sensitive column name. The new issue occurs through MySQL
8.0.17, so the general logic of the 88718 fix remains in place.
.. seealso::
https://bugs.mysql.com/bug.php?id=96365 - upstream bug
.. change::
:tags: usecase, mssql
:tickets: 4782
Added new :func:`.mssql.try_cast` construct for SQL Server which emits
"TRY_CAST" syntax. Pull request courtesy Leonel Atencio.
.. change::
:tags: bug, orm
:tickets: 4803
Fixed bug where using :meth:`.Query.first` or a slice expression in
conjunction with a query that has an expression based "offset" applied
would raise TypeError, due to an "or" conditional against "offset" that did
not expect it to be a SQL expression as opposed to an integer or None.
.. changelog::
```
Links
- PyPI: https://pypi.org/project/sqlalchemy
- Changelog: https://pyup.io/changelogs/sqlalchemy/
- Homepage: http://www.sqlalchemy.org
Changelog
### 5.2.2
```
=========================
Bug Fixes
---------
- `5206 <https://github.com/pytest-dev/pytest/issues/5206>`_: Fix ``--nf`` to not forget about known nodeids with partial test selection.
- `5906 <https://github.com/pytest-dev/pytest/issues/5906>`_: Fix crash with ``KeyboardInterrupt`` during ``--setup-show``.
- `5946 <https://github.com/pytest-dev/pytest/issues/5946>`_: Fixed issue when parametrizing fixtures with numpy arrays (and possibly other sequence-like types).
- `6044 <https://github.com/pytest-dev/pytest/issues/6044>`_: Properly ignore ``FileNotFoundError`` exceptions when trying to remove old temporary directories,
for instance when multiple processes try to remove the same directory (common with ``pytest-xdist``
for example).
```
### 5.2.1
```
=========================
Bug Fixes
---------
- `5902 <https://github.com/pytest-dev/pytest/issues/5902>`_: Fix warnings about deprecated ``cmp`` attribute in ``attrs>=19.2``.
```
### 5.2.0
```
=========================
Deprecations
------------
- `1682 <https://github.com/pytest-dev/pytest/issues/1682>`_: Passing arguments to pytest.fixture() as positional arguments is deprecated - pass them
as a keyword argument instead.
Features
--------
- `1682 <https://github.com/pytest-dev/pytest/issues/1682>`_: The ``scope`` parameter of ``pytest.fixture`` can now be a callable that receives
the fixture name and the ``config`` object as keyword-only parameters.
See `the docs <https://docs.pytest.org/en/latest/fixture.htmldynamic-scope>`__ for more information.
- `5764 <https://github.com/pytest-dev/pytest/issues/5764>`_: New behavior of the ``--pastebin`` option: failures to connect to the pastebin server are reported, without failing the pytest run
Bug Fixes
---------
- `5806 <https://github.com/pytest-dev/pytest/issues/5806>`_: Fix "lexer" being used when uploading to bpaste.net from ``--pastebin`` to "text".
- `5884 <https://github.com/pytest-dev/pytest/issues/5884>`_: Fix ``--setup-only`` and ``--setup-show`` for custom pytest items.
Trivial/Internal Changes
------------------------
- `5056 <https://github.com/pytest-dev/pytest/issues/5056>`_: The HelpFormatter uses ``py.io.get_terminal_width`` for better width detection.
```
### 5.1.3
```
=========================
Bug Fixes
---------
- `5807 <https://github.com/pytest-dev/pytest/issues/5807>`_: Fix pypy3.6 (nightly) on windows.
- `5811 <https://github.com/pytest-dev/pytest/issues/5811>`_: Handle ``--fulltrace`` correctly with ``pytest.raises``.
- `5819 <https://github.com/pytest-dev/pytest/issues/5819>`_: Windows: Fix regression with conftest whose qualified name contains uppercase
characters (introduced by 5792).
```
### 5.1.2
```
=========================
Bug Fixes
---------
- `2270 <https://github.com/pytest-dev/pytest/issues/2270>`_: Fixed ``self`` reference in function-scoped fixtures defined plugin classes: previously ``self``
would be a reference to a *test* class, not the *plugin* class.
- `570 <https://github.com/pytest-dev/pytest/issues/570>`_: Fixed long standing issue where fixture scope was not respected when indirect fixtures were used during
parametrization.
- `5782 <https://github.com/pytest-dev/pytest/issues/5782>`_: Fix decoding error when printing an error response from ``--pastebin``.
- `5786 <https://github.com/pytest-dev/pytest/issues/5786>`_: Chained exceptions in test and collection reports are now correctly serialized, allowing plugins like
``pytest-xdist`` to display them properly.
- `5792 <https://github.com/pytest-dev/pytest/issues/5792>`_: Windows: Fix error that occurs in certain circumstances when loading
``conftest.py`` from a working directory that has casing other than the one stored
in the filesystem (e.g., ``c:\test`` instead of ``C:\test``).
```
### 5.1.1
```
=========================
Bug Fixes
---------
- `5751 <https://github.com/pytest-dev/pytest/issues/5751>`_: Fixed ``TypeError`` when importing pytest on Python 3.5.0 and 3.5.1.
```
### 5.1.0
```
=========================
Removals
--------
- `5180 <https://github.com/pytest-dev/pytest/issues/5180>`_: As per our policy, the following features have been deprecated in the 4.X series and are now
removed:
* ``Request.getfuncargvalue``: use ``Request.getfixturevalue`` instead.
* ``pytest.raises`` and ``pytest.warns`` no longer support strings as the second argument.
* ``message`` parameter of ``pytest.raises``.
* ``pytest.raises``, ``pytest.warns`` and ``ParameterSet.param`` now use native keyword-only
syntax. This might change the exception message from previous versions, but they still raise
``TypeError`` on unknown keyword arguments as before.
* ``pytest.config`` global variable.
* ``tmpdir_factory.ensuretemp`` method.
* ``pytest_logwarning`` hook.
* ``RemovedInPytest4Warning`` warning type.
* ``request`` is now a reserved name for fixtures.
For more information consult
`Deprecations and Removals <https://docs.pytest.org/en/latest/deprecations.html>`__ in the docs.
- `5565 <https://github.com/pytest-dev/pytest/issues/5565>`_: Removed unused support code for `unittest2 <https://pypi.org/project/unittest2/>`__.
The ``unittest2`` backport module is no longer
necessary since Python 3.3+, and the small amount of code in pytest to support it also doesn't seem
to be used: after removed, all tests still pass unchanged.
Although our policy is to introduce a deprecation period before removing any features or support
for third party libraries, because this code is apparently not used
at all (even if ``unittest2`` is used by a test suite executed by pytest), it was decided to
remove it in this release.
If you experience a regression because of this, please
`file an issue <https://github.com/pytest-dev/pytest/issues/new>`__.
- `5615 <https://github.com/pytest-dev/pytest/issues/5615>`_: ``pytest.fail``, ``pytest.xfail`` and ``pytest.skip`` no longer support bytes for the message argument.
This was supported for Python 2 where it was tempting to use ``"message"``
instead of ``u"message"``.
Python 3 code is unlikely to pass ``bytes`` to these functions. If you do,
please decode it to an ``str`` beforehand.
Features
--------
- `5564 <https://github.com/pytest-dev/pytest/issues/5564>`_: New ``Config.invocation_args`` attribute containing the unchanged arguments passed to ``pytest.main()``.
- `5576 <https://github.com/pytest-dev/pytest/issues/5576>`_: New `NUMBER <https://docs.pytest.org/en/latest/doctest.htmlusing-doctest-options>`__
option for doctests to ignore irrelevant differences in floating-point numbers.
Inspired by Sébastien Boisgérault's `numtest <https://github.com/boisgera/numtest>`__
extension for doctest.
Improvements
------------
- `5471 <https://github.com/pytest-dev/pytest/issues/5471>`_: JUnit XML now includes a timestamp and hostname in the testsuite tag.
- `5707 <https://github.com/pytest-dev/pytest/issues/5707>`_: Time taken to run the test suite now includes a human-readable representation when it takes over
60 seconds, for example::
===== 2 failed in 102.70s (0:01:42) =====
Bug Fixes
---------
- `4344 <https://github.com/pytest-dev/pytest/issues/4344>`_: Fix RuntimeError/StopIteration when trying to collect package with "__init__.py" only.
- `5115 <https://github.com/pytest-dev/pytest/issues/5115>`_: Warnings issued during ``pytest_configure`` are explicitly not treated as errors, even if configured as such, because it otherwise completely breaks pytest.
- `5477 <https://github.com/pytest-dev/pytest/issues/5477>`_: The XML file produced by ``--junitxml`` now correctly contain a ``<testsuites>`` root element.
- `5524 <https://github.com/pytest-dev/pytest/issues/5524>`_: Fix issue where ``tmp_path`` and ``tmpdir`` would not remove directories containing files marked as read-only,
which could lead to pytest crashing when executed a second time with the ``--basetemp`` option.
- `5537 <https://github.com/pytest-dev/pytest/issues/5537>`_: Replace ``importlib_metadata`` backport with ``importlib.metadata`` from the
standard library on Python 3.8+.
- `5578 <https://github.com/pytest-dev/pytest/issues/5578>`_: Improve type checking for some exception-raising functions (``pytest.xfail``, ``pytest.skip``, etc)
so they provide better error messages when users meant to use marks (for example ``pytest.xfail``
instead of ``pytest.mark.xfail``).
- `5606 <https://github.com/pytest-dev/pytest/issues/5606>`_: Fixed internal error when test functions were patched with objects that cannot be compared
for truth values against others, like ``numpy`` arrays.
- `5634 <https://github.com/pytest-dev/pytest/issues/5634>`_: ``pytest.exit`` is now correctly handled in ``unittest`` cases.
This makes ``unittest`` cases handle ``quit`` from pytest's pdb correctly.
- `5650 <https://github.com/pytest-dev/pytest/issues/5650>`_: Improved output when parsing an ini configuration file fails.
- `5701 <https://github.com/pytest-dev/pytest/issues/5701>`_: Fix collection of ``staticmethod`` objects defined with ``functools.partial``.
- `5734 <https://github.com/pytest-dev/pytest/issues/5734>`_: Skip async generator test functions, and update the warning message to refer to ``async def`` functions.
Improved Documentation
----------------------
- `5669 <https://github.com/pytest-dev/pytest/issues/5669>`_: Add docstring for ``Testdir.copy_example``.
Trivial/Internal Changes
------------------------
- `5095 <https://github.com/pytest-dev/pytest/issues/5095>`_: XML files of the ``xunit2`` family are now validated against the schema by pytest's own test suite
to avoid future regressions.
- `5516 <https://github.com/pytest-dev/pytest/issues/5516>`_: Cache node splitting function which can improve collection performance in very large test suites.
- `5603 <https://github.com/pytest-dev/pytest/issues/5603>`_: Simplified internal ``SafeRepr`` class and removed some dead code.
- `5664 <https://github.com/pytest-dev/pytest/issues/5664>`_: When invoking pytest's own testsuite with ``PYTHONDONTWRITEBYTECODE=1``,
the ``test_xfail_handling`` test no longer fails.
- `5684 <https://github.com/pytest-dev/pytest/issues/5684>`_: Replace manual handling of ``OSError.errno`` in the codebase by new ``OSError`` subclasses (``PermissionError``, ``FileNotFoundError``, etc.).
```
Links
- PyPI: https://pypi.org/project/pytest
- Changelog: https://pyup.io/changelogs/pytest/
- Homepage: https://docs.pytest.org/en/latest/
Changelog
### 2.8.1
```
------------------
* Fixed `348 <https://github.com/pytest-dev/pytest-cov/issues/348>`_ -
regression when only certain reports (html or xml) are used then ``--cov-fail-under`` always fails.
```
### 2.8.0
```
------------------
* Fixed ``RecursionError`` that can occur when using
`cleanup_on_signal <https://pytest-cov.readthedocs.io/en/latest/subprocess-support.htmlif-you-got-custom-signal-handling>`__ or
`cleanup_on_sigterm <https://pytest-cov.readthedocs.io/en/latest/subprocess-support.htmlif-you-got-custom-signal-handling>`__.
See: `294 <https://github.com/pytest-dev/pytest-cov/issues/294>`_.
The 2.7.x releases of pytest-cov should be considered broken regarding aforementioned cleanup API.
* Added compatibility with future xdist release that deprecates some internals
(match pytest-xdist master/worker terminology).
Contributed by Thomas Grainger in `321 <https://github.com/pytest-dev/pytest-cov/pull/321>`_
* Fixed breakage that occurs when multiple reporting options are used.
Contributed by Thomas Grainger in `338 <https://github.com/pytest-dev/pytest-cov/pull/338>`_.
* Changed internals to use a stub instead of ``os.devnull``.
Contributed by Thomas Grainger in `332 <https://github.com/pytest-dev/pytest-cov/pull/332>`_.
* Added support for Coverage 5.0.
Contributed by Ned Batchelder in `319 <https://github.com/pytest-dev/pytest-cov/pull/319>`_.
* Added support for float values in ``--cov-fail-under``.
Contributed by Martín Gaitán in `311 <https://github.com/pytest-dev/pytest-cov/pull/311>`_.
* Various documentation fixes. Contributed by
Juanjo Bazán,
Andrew Murray and
Albert Tugushev in
`298 <https://github.com/pytest-dev/pytest-cov/pull/298>`_,
`299 <https://github.com/pytest-dev/pytest-cov/pull/299>`_ and
`307 <https://github.com/pytest-dev/pytest-cov/pull/307>`_.
* Various testing improvements. Contributed by
Ned Batchelder,
Daniel Hahler,
Ionel Cristian Mărieș and
Hugo van Kemenade in
`313 <https://github.com/pytest-dev/pytest-cov/pull/313>`_,
`314 <https://github.com/pytest-dev/pytest-cov/pull/314>`_,
`315 <https://github.com/pytest-dev/pytest-cov/pull/315>`_,
`316 <https://github.com/pytest-dev/pytest-cov/pull/316>`_,
`325 <https://github.com/pytest-dev/pytest-cov/pull/325>`_,
`326 <https://github.com/pytest-dev/pytest-cov/pull/326>`_,
`334 <https://github.com/pytest-dev/pytest-cov/pull/334>`_ and
`335 <https://github.com/pytest-dev/pytest-cov/pull/335>`_.
* Added the ``--cov-context`` CLI options that enables coverage contexts. Only works with coverage 5.0+.
Contributed by Ned Batchelder in `345 <https://github.com/pytest-dev/pytest-cov/pull/345>`_.
```
Links
- PyPI: https://pypi.org/project/pytest-cov
- Changelog: https://pyup.io/changelogs/pytest-cov/
- Repo: https://github.com/pytest-dev/pytest-cov
Update astropy from 3.2.1 to 3.2.3.
Changelog
### 3.2.3 ``` ================== Other Changes and Additions --------------------------- - Updated IERS A URLs due to USNO prolonged maintenance. [9443] ``` ### 3.2.2 ``` ================== Bug fixes --------- astropy.convolution ^^^^^^^^^^^^^^^^^^^ - Fixed a bug in ``discretize_oversample_1D/2D()`` from ``astropy.convolution.utils``, which might occasionally introduce unexpected oversampling grid dimensions due to a numerical precision issue. [9293] - Fixed a bug [9168] where having a kernel defined using unitless astropy quantity objects would result in a crash [9300] astropy.coordinates ^^^^^^^^^^^^^^^^^^^ - Fix concatenation of representations for cases where the units were different. [8877] - Check for NaN values in catalog and match coordinates before building and querying the ``KDTree`` for coordinate matching. [9007] - Fix sky coordinate matching when a dimensionless distance is provided. [9008] - Raise a faster and more meaningful error message when differential data units are not compatible with a containing representation's units. [9064] - Changed the timescale in ICRS to CIRS from 'tdb' to 'tt' conversion and vice-versa, as the erfa function that gets called in the process, pnm06a accepts time in TT. [9079] astropy.io.ascii ^^^^^^^^^^^^^^^^ - Fixed the fast reader when used in parallel and with the multiprocessing 'spawn' method (which is the default on MacOS X with Python 3.8 and later), and enable parallel fast reader on Windows. [8853] astropy.io.fits ^^^^^^^^^^^^^^^ - Fixes bug where an invalid TRPOS<n> keyword was being generated for FITS time column when no location was available. [8784] - Fixed a wrong exception when converting a Table with a unit that is not FITS compliant and not convertible to a string using ``format='fits'``. [8906] - Fixed an issue with A3DTABLE extension that could not be read. [9012] - Fixed the update of the header when creating GroupsHDU from data. [9216] astropy.nddata ^^^^^^^^^^^^^^ - Fix to ``add_array``, which now accepts ``array_small`` having dimensions equal to ``array_large``, instead of only allowing smaller sizes of arrays. [9118] astropy.stats ^^^^^^^^^^^^^ - Fixed ``median_absolute_deviation`` for the case where ``ignore_nan=True`` and an input masked array contained both NaNs and infs. [9307] astropy.table ^^^^^^^^^^^^^ - Comparisons between ``Column`` instances and ``Quantity`` will now correctly take into account the unit (as was already the case for regular operations such as addition). [8904] astropy.time ^^^^^^^^^^^^ - Allow ``Time`` to be initialized with an empty value for all formats. [8854] - Fixed a troubling bug in which ``Time`` could loose precision, with deviations of 300 ns. [9328] astropy.timeseries ^^^^^^^^^^^^^^^^^^ - Fixed handling of ``Quantity`` input data for all methods of ``LombScarge.false_alarm_probabilty``. [9246] astropy.units ^^^^^^^^^^^^^ - Allow conversion of ``Column`` with logarithmic units to a suitable ``Quantity`` subclass if ``subok=True``. [9188] - Ensured that we simplify powers to smaller denominators if that is consistent within rounding precision. [9267] - Ensured that the powers shown in a unit's repr are always correct, not oversimplified. [9267] astropy.utils ^^^^^^^^^^^^^ - Fixed ``find_api_page`` access by using custom request headers and HTTPS when version is specified. [9032] - Make ``download_file`` (and by extension ``get_readable_fileobj`` and others) check the size of downloaded files against the size claimed by the server. [9302] - Fix ``find_current_module`` so that it works properly if astropy is being used inside a bundle such as that produced by PyInstaller. [8845] - Fix path to renamed classes, which previously included duplicate path/module information under certain circumstances. [8845] astropy.visualization ^^^^^^^^^^^^^^^^^^^^^ - Silence numpy runtime warnings in ``WCSAxes`` when drawing grids. [8882] astropy.wcs ^^^^^^^^^^^ - Fixed equality test between ``cunit`` where the first element was equal but the following elements differed. [9154] - Fixed a crash while loading a WCS from headers containing duplicate SIP keywords. [8893] - Fixed a possible buffer overflow when using too large negative indices for ``cunit`` or ``ctype`` [9151] - Fixed reference counting in ``WCSBase.__init__`` [9166] - Fix ``SlicedLowLevelWCS`` ``world_to_pixel_values`` and ``pixel_to_world_values`` when inputs need broadcasting to the same shape. (i.e. when one input is sliced out) [9250] - Fixed a bug that caused ``WCS.array_shape``, ``WCS.pixel_shape`` and ``WCS.pixel_bounds`` to be incorrect after using ``WCS.sub``. [9095] Other Changes and Additions --------------------------- - Fixed a bug that caused files outside of the astropy module directory to be included as package data, resulting in some cases in errors when doing repeated builds. [9039] ```Links
- PyPI: https://pypi.org/project/astropy - Changelog: https://pyup.io/changelogs/astropy/ - Homepage: http://astropy.orgUpdate ephem from 3.7.6.0 to 3.7.7.0.
The bot wasn't able to find a changelog for this release. Got an idea?
Links
- PyPI: https://pypi.org/project/ephem - Homepage: http://rhodesmill.org/pyephem/Update joblib from 0.13.2 to 0.14.0.
Changelog
### 0.14.0 ``` -------------- - Improved the load balancing between workers to avoid stranglers caused by an excessively large batch size when the task duration is varying significantly (because of the combined use of ``joblib.Parallel`` and ``joblib.Memory`` with a partially warmed cache for instance). https://github.com/joblib/joblib/pull/899 - Add official support for Python 3.8: fixed protocol number in `Hasher` and updated tests. - Fix a deadlock when using the dask backend (when scattering large numpy arrays). https://github.com/joblib/joblib/pull/914 - Warn users that they should never use `joblib.load` with files from untrusted sources. Fix security related API change introduced in numpy 1.6.3 that would prevent using joblib with recent numpy versions. https://github.com/joblib/joblib/pull/879 - Upgrade to cloudpickle 1.1.1 that add supports for the upcoming Python 3.8 release among other things. https://github.com/joblib/joblib/pull/878 - Fix semaphore availability checker to avoid spawning resource trackers on module import. https://github.com/joblib/joblib/pull/893 - Fix the oversubscription protection to only protect against nested `Parallel` calls. This allows `joblib` to be run in background threads. https://github.com/joblib/joblib/pull/934 - Fix `ValueError` (negative dimensions) when pickling large numpy arrays on Windows. https://github.com/joblib/joblib/pull/920 - Upgrade to loky 2.6.0 that add supports for the setting environment variables in child before loading any module. https://github.com/joblib/joblib/pull/940 - Fix the oversubscription protection for native libraries using threadpools (OpenBLAS, MKL, Blis and OpenMP runtimes). The maximal number of threads is can now be set in children using the ``inner_max_num_threads`` in ``parallel_backend``. It defaults to ``cpu_count() // n_jobs``. https://github.com/joblib/joblib/pull/940 ```Links
- PyPI: https://pypi.org/project/joblib - Changelog: https://pyup.io/changelogs/joblib/ - Docs: https://joblib.readthedocs.ioUpdate numba from 0.45.0 to 0.46.0.
Changelog
### 0.46.0 ``` -------------- This release significantly reworked one of the main parts of Numba, the compiler pipeline, to make it more extensible and easier to use. The purpose of this was to continue enhancing Numba's ability for use as a compiler toolkit. In a similar vein, Numba now has an extension registration mechanism to allow other Numba-using projects to automatically have their Numba JIT compilable functions discovered. There were also a number of other related compiler toolkit enhancement added along with some more NumPy features and a lot of bug fixes. This release has updated the CUDA Array Interface specification to version 2, which clarifies the `strides` attribute for C-contiguous arrays and specifies the treatment for zero-size arrays. The implementation in Numba has been changed and may affect downstream packages relying on the old behavior (see issue 4661). Enhancements from user contributed PRs (with thanks!): * Aaron Meurer fixed some Python issues in the code base in 4345 and 4341. * Ashwin Srinath fixed a CUDA performance bug via 4576. * Ethan Pronovost added support for triangular indices functions in 4601 (the NumPy functions ``tril_indices``, ``tril_indices_from``, ``triu_indices``, and ``triu_indices_from``). * Gerald Dalley fixed a tear down race occurring in Python 2. * Gregory R. Lee fixed the use of deprecated ``inspect.getargspec``. * Guilherme Leobas contributed five PRs, adding support for ``np.append`` and ``np.count_nonzero`` in 4518 and 4386. The typed List was fixed to accept unsigned integers in 4510. 4463 made a fix to NamedTuple internals and 4397 updated the docs for ``np.sum``. * James Bourbeau added a new feature to permit the automatic application of the `jit` decorator to a whole module in 4331. Also some small fixes to the docs and the code base were made in 4447 and 4433, and a fix to inplace array operation in 4228. * Jim Crist fixed a bug in the rendering of patched errors in 4464. * Leo Fang updated the CUDA Array Interface contract in 4609. * Pearu Peterson added support for Unicode based NumPy arrays in 4425. * Peter Andreas Entschev fixed a CUDA concurrency bug in 4581. * Lucio Fernandez-Arjona extended Numba's ``np.sum`` support to now accept the ``dtype`` kwarg in 4472. * Pedro A. Morales Maries added support for ``np.cross`` in 4128 and also added the necessary extension ``numba.numpy_extensions.cross2d`` in 4595. * David Hoese, Eric Firing, Joshua Adelman, and Juan Nunez-Iglesias all made documentation fixes in 4565, 4482, 4455, 4375 respectively. * Vyacheslav Smirnov and Rujal Desai enabled support for ``count()`` on unicode strings in 4606. General Enhancements: * PR 4113: Add rewrite for semantic constants. * PR 4128: Add np.cross support * PR 4162: Make IR comparable and legalize it. * PR 4208: R&D inlining, jitted and overloaded. * PR 4331: Automatic JIT of called functions * PR 4353: Inspection tool to check what numba supports * PR 4386: Implement np.count_nonzero * PR 4425: Unicode array support * PR 4427: Entrypoints for numba extensions * PR 4467: Literal dispatch * PR 4472: Allow dtype input argument in np.sum * PR 4513: New compiler. * PR 4518: add support for np.append * PR 4554: Refactor NRT C-API * PR 4556: 0.46 scheduled deprecations * PR 4567: Add env var to disable performance warnings. * PR 4568: add np.array_equal support * PR 4595: Implement numba.cross2d * PR 4601: Add triangular indices functions * PR 4606: Enable support for count() method for unicode string Fixes: * PR 4228: Fix inplace operator error for arrays * PR 4282: Detect and raise unsupported on generator expressions * PR 4305: Don't allow the allocation of mutable objects written into a container to be hoisted. * PR 4311: Avoid deprecated use of inspect.getargspec * PR 4328: Replace GC macro with function call * PR 4330: Loosen up typed container casting checks * PR 4341: Fix some coding lines at the top of some files (utf8 -> utf-8) * PR 4345: Replace "import \*" with explicit imports in numba/types * PR 4346: Fix incorrect alg in isupper for ascii strings. * PR 4349: test using jitclass in typed-list * PR 4361: Add allocation hoisting info to LICM section at diagnostic L4 * PR 4366: Offset search box to avoid wrapping on some pages with Safari. Fixes 4365. * PR 4372: Replace all "except BaseException" with "except Exception". * PR 4407: Restore the "free" conda channel for NumPy 1.10 support. * PR 4408: Add lowering for constant bytes. * PR 4409: Add exception chaining for better error context * PR 4411: Name of type should not contain user facing description for debug. * PR 4412: Fix 4387. Limit the number of return types for recursive functions * PR 4426: Fixed two module teardown races in py2. * PR 4431: Fix and test numpy.random.random_sample(n) for np117 * PR 4463: NamedTuple - Raises an error on non-iterable elements * PR 4464: Add a newline in patched errors * PR 4474: Fix liveness for remove dead of parfors (and other IR extensions) * PR 4510: Make List.__getitem__ accept unsigned parameters * PR 4512: Raise specific error at typing time for iteration on >1D array. * PR 4532: Fix static_getitem with Literal type as index * PR 4547: Update to inliner cost model information. * PR 4557: Use specific random number seed when generating arbitrary test data * PR 4559: Adjust test timeouts * PR 4564: Skip unicode array tests on ppc64le that trigger an LLVM bug * PR 4621: Fix packaging issue due to missing numba/cext * PR 4623: Fix issue 4520 due to storage model mismatch * PR 4644: Updates for llvmlite 0.30.0 CUDA Enhancements/Fixes: * PR 4410: Fix 4111. cudasim mishandling recarray * PR 4576: Replace use of `np.prod` with `functools.reduce` for computing size from shape * PR 4581: Prevent taking the GIL in ForAll * PR 4592: Fix 4589. Just pass NULL for b2d_func for constant dynamic sharedmem * PR 4609: Update CUDA Array Interface & Enforce Numba compliance * PR 4619: Implement math.{degrees, radians} for the CUDA target. * PR 4675: Bump cuda array interface to version 2 Documentation Updates: * PR 4317: Add docs for ARMv8/AArch64 * PR 4318: Add supported platforms to the docs. Closes 4316 * PR 4375: Add docstrings to inspect methods * PR 4388: Update Python 2.7 EOL statement * PR 4397: Add note about np.sum * PR 4447: Minor parallel performance tips edits * PR 4455: Clarify docs for typed dict with regard to arrays * PR 4482: Fix example in guvectorize docstring. * PR 4541: fix two typos in architecture.rst * PR 4548: Document numba.extending.intrinsic and inlining. * PR 4565: Fix typo in jit-compilation docs * PR 4607: add dependency list to docs * PR 4614: Add documentation for implementing new compiler passes. CI Updates: * PR 4415: Make 32bit incremental builds on linux not use free channel * PR 4433: Removes stale azure comment * PR 4493: Fix Overload Inliner wrt CUDA Intrinsics * PR 4593: Enable Azure CI batching Contributors: * Aaron Meurer * Ashwin Srinath * David Hoese * Ehsan Totoni (core dev) * Eric Firing * Ethan Pronovost * Gerald Dalley * Gregory R. Lee * Guilherme Leobas * James Bourbeau * Jim Crist * Joshua Adelman * Juan Nunez-Iglesias * Leo Fang * Lucio Fernandez-Arjona * Pearu Peterson * Pedro A. Morales Marie * Peter Andreas Entschev * Rujal Desai * Siu Kwan Lam (core dev) * Stan Seibert (core dev) * Stuart Archibald (core dev) * Todd A. Anderson (core dev) * Valentin Haenel (core dev) * Vyacheslav Smirnov ``` ### 0.45.1 ``` -------------- This patch release addresses some regressions reported in the 0.45.0 release and ```Links
- PyPI: https://pypi.org/project/numba - Changelog: https://pyup.io/changelogs/numba/ - Repo: http://numba.github.comUpdate numpy from 1.17.0 to 1.17.3.
The bot wasn't able to find a changelog for this release. Got an idea?
Links
- PyPI: https://pypi.org/project/numpy - Homepage: https://www.numpy.orgUpdate multiprocess from 0.70.8 to 0.70.9.
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.9/multiprocess-0.70.9.tar.gz - Homepage: https://pypi.org/project/multiprocessUpdate pandas from 0.25.0 to 0.25.3.
The bot wasn't able to find a changelog for this release. Got an idea?
Links
- PyPI: https://pypi.org/project/pandas - Homepage: http://pandas.pydata.orgUpdate scipy from 1.3.0 to 1.3.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.orgUpdate sqlalchemy from 1.3.6 to 1.3.10.
Changelog
### 1.3.10 ``` :include_notes_from: unreleased_13 .. changelog:: ``` ### 1.3.9 ``` :released: October 4, 2019 .. change:: :tags: usecase, engine :tickets: 4857 Added new :func:`.create_engine` parameter :paramref:`.create_engine.max_identifier_length`. This overrides the dialect-coded "max identifier length" in order to accommodate for databases that have recently changed this length and the SQLAlchemy dialect has not yet been adjusted to detect for that version. This parameter interacts with the existing :paramref:`.create_engine.label_length` parameter in that it establishes the maximum (and default) value for anonymously generated labels. Additionally, post-connection detection of max identifier lengths has been added to the dialect system. This feature is first being used by the Oracle dialect. .. seealso:: :ref:`oracle_max_identifier_lengths` - in the Oracle dialect documentation .. change:: :tags: usecase, oracle :tickets: 4857 The Oracle dialect now emits a warning if Oracle version 12.2 or greater is used, and the :paramref:`.create_engine.max_identifier_length` parameter is not set. The version in this specific case defaults to that of the "compatibility" version set in the Oracle server configuration, not the actual server version. In version 1.4, the default max_identifier_length for 12.2 or greater will move to 128 characters. In order to maintain forwards compatibility, applications should set :paramref:`.create_engine.max_identifier_length` to 30 in order to maintain the same length behavior, or to 128 in order to test the upcoming behavior. This length determines among other things how generated constraint names are truncated for statements like ``CREATE CONSTRAINT`` and ``DROP CONSTRAINT``, which means a the new length may produce a name-mismatch against a name that was generated with the old length, impacting database migrations. .. seealso:: :ref:`oracle_max_identifier_lengths` - in the Oracle dialect documentation .. change:: :tags: usecase, sqlite :tickets: 4863 Added support for sqlite "URI" connections, which allow for sqlite-specific flags to be passed in the query string such as "read only" for Python sqlite3 drivers that support this. .. seealso:: :ref:`pysqlite_uri_connections` .. change:: :tags: bug, tests :tickets: 4285 Fixed unit test regression released in 1.3.8 that would cause failure for Oracle, SQL Server and other non-native ENUM platforms due to new enumeration tests added as part of :ticket:`4285` enum sortability in the unit of work; the enumerations created constraints that were duplicated on name. .. change:: :tags: bug, oracle :tickets: 4886 Restored adding cx_Oracle.DATETIME to the setinputsizes() call when a SQLAlchemy :class:`.Date`, :class:`.DateTime` or :class:`.Time` datatype is used, as some complex queries require this to be present. This was removed in the 1.2 series for arbitrary reasons. .. change:: :tags: bug, mssql :tickets: 4883 Added identifier quoting to the schema name applied to the "use" statement which is invoked when a SQL Server multipart schema name is used within a :class:`.Table` that is being reflected, as well as for :class:`.Inspector` methods such as :meth:`.Inspector.get_table_names`; this accommodates for special characters or spaces in the database name. Additionally, the "use" statement is not emitted if the current database matches the target owner database name being passed. .. change:: :tags: bug, orm :tickets: 4872 Fixed regression in selectinload loader strategy caused by :ticket:`4775` (released in version 1.3.6) where a many-to-one attribute of None would no longer be populated by the loader. While this was usually not noticeable due to the lazyloader populating None upon get, it would lead to a detached instance error if the object were detached. .. change:: :tags: bug, orm :tickets: 4873 Passing a plain string expression to :meth:`.Session.query` is deprecated, as all string coercions were removed in :ticket:`4481` and this one should have been included. The :func:`.literal_column` function may be used to produce a textual column expression. .. change:: :tags: usecase, sql :tickets: 4847 Added an explicit error message for the case when objects passed to :class:`.Table` are not :class:`.SchemaItem` objects, rather than resolving to an attribute error. .. change:: :tags: bug, orm :tickets: 4890 A warning is emitted for a condition in which the :class:`.Session` may implicitly swap an object out of the identity map for another one with the same primary key, detaching the old one, which can be an observed result of load operations which occur within the :meth:`.SessionEvents.after_flush` hook. The warning is intended to notify the user that some special condition has caused this to happen and that the previous object may not be in the expected state. .. change:: :tags: bug, sql :tickets: 4837 Characters that interfere with "pyformat" or "named" formats in bound parameters, namely ``%, (, )`` and the space character, as well as a few other typically undesirable characters, are stripped early for a :func:`.bindparam` that is using an anonymized name, which is typically generated automatically from a named column which itself includes these characters in its name and does not use a ``.key``, so that they do not interfere either with the SQLAlchemy compiler's use of string formatting or with the driver-level parsing of the parameter, both of which could be demonstrated before the fix. The change only applies to anonymized parameter names that are generated and consumed internally, not end-user defined names, so the change should have no impact on any existing code. Applies in particular to the psycopg2 driver which does not otherwise quote special parameter names, but also strips leading underscores to suit Oracle (but not yet leading numbers, as some anon parameters are currently entirely numeric/underscore based); Oracle in any case continues to quote parameter names that include special characters. .. changelog:: ``` ### 1.3.8 ``` :released: August 27, 2019 .. change:: :tags: bug, orm :tickets: 4823 Fixed bug where :class:`.Load` objects were not pickleable due to mapper/relationship state in the internal context dictionary. These objects are now converted to picklable using similar techniques as that of other elements within the loader option system that have long been serializable. .. change:: :tags: bug, postgresql :tickets: 4623 Revised the approach for the just added support for the psycopg2 "execute_values()" feature added in 1.3.7 for :ticket:`4623`. The approach relied upon a regular expression that would fail to match for a more complex INSERT statement such as one which had subqueries involved. The new approach matches exactly the string that was rendered as the VALUES clause. .. change:: :tags: usecase, orm :tickets: 4285 Added support for the use of an :class:`.Enum` datatype using Python pep-435 enumeration objects as values for use as a primary key column mapped by the ORM. As these values are not inherently sortable, as required by the ORM for primary keys, a new :attr:`.TypeEngine.sort_key_function` attribute is added to the typing system which allows any SQL type to implement a sorting for Python objects of its type which is consulted by the unit of work. The :class:`.Enum` type then defines this using the database value of a given enumeration. The sorting scheme can be also be redefined by passing a callable to the :paramref:`.Enum.sort_key_function` parameter. Pull request courtesy Nicolas Caniart. .. change:: :tags: bug, engine :tickets: 4807 Fixed an issue whereby if the dialect "initialize" process which occurs on first connect would encounter an unexpected exception, the initialize process would fail to complete and then no longer attempt on subsequent connection attempts, leaving the dialect in an un-initialized, or partially initialized state, within the scope of parameters that need to be established based on inspection of a live connection. The "invoke once" logic in the event system has been reworked to accommodate for this occurrence using new, private API features that establish an "exec once" hook that will continue to allow the initializer to fire off on subsequent connections, until it completes without raising an exception. This does not impact the behavior of the existing ``once=True`` flag within the event system. .. change:: :tags: bug, sqlite, reflection :tickets: 4810 Fixed bug where a FOREIGN KEY that was set up to refer to the parent table by table name only without the column names would not correctly be reflected as far as setting up the "referred columns", since SQLite's PRAGMA does not report on these columns if they weren't given explicitly. For some reason this was harcoded to assume the name of the local column, which might work for some cases but is not correct. The new approach reflects the primary key of the referred table and uses the constraint columns list as the referred columns list, if the remote column(s) aren't present in the reflected pragma directly. .. change:: :tags: bug, postgresql :tickets: 4822 Fixed bug where Postgresql operators such as :meth:`.postgresql.ARRAY.Comparator.contains` and :meth:`.postgresql.ARRAY.Comparator.contained_by` would fail to function correctly for non-integer values when used against a :class:`.postgresql.array` object, due to an erroneous assert statement. .. change:: :tags: feature, engine :tickets: 4815 Added new parameter :paramref:`.create_engine.hide_parameters` which when set to True will cause SQL parameters to no longer be logged, nor rendered in the string representation of a :class:`.StatementError` object. .. change:: :tags: usecase, postgresql :tickets: 4824 Added support for reflection of CHECK constraints that include the special PostgreSQL qualifier "NOT VALID", which can be present for CHECK constraints that were added to an exsiting table with the directive that they not be applied to existing data in the table. The PostgreSQL dictionary for CHECK constraints as returned by :meth:`.Inspector.get_check_constraints` may include an additional entry ``dialect_options`` which within will contain an entry ``"not_valid": True`` if this symbol is detected. Pull request courtesy Bill Finn. .. changelog:: ``` ### 1.3.7 ``` :released: August 14, 2019 .. change:: :tags: bug, sql :tickets: 4778 Fixed issue where :class:`.Index` object which contained a mixture of functional expressions which were not resolvable to a particular column, in combination with string-based column names, would fail to initialize its internal state correctly leading to failures during DDL compilation. .. change:: :tags: bug, sqlite :tickets: 4798 The dialects that support json are supposed to take arguments ``json_serializer`` and ``json_deserializer`` at the create_engine() level, however the SQLite dialect calls them ``_json_serilizer`` and ``_json_deserilalizer``. The names have been corrected, the old names are accepted with a change warning, and these parameters are now documented as :paramref:`.create_engine.json_serializer` and :paramref:`.create_engine.json_deserializer`. .. change:: :tags: bug, mysql :tickets: 4804 The MySQL dialects will emit "SET NAMES" at the start of a connection when charset is given to the MySQL driver, to appease an apparent behavior observed in MySQL 8.0 that raises a collation error when a UNION includes string columns unioned against columns of the form CAST(NULL AS CHAR(..)), which is what SQLAlchemy's polymorphic_union function does. The issue seems to have affected PyMySQL for at least a year, however has recently appeared as of mysqlclient 1.4.4 based on changes in how this DBAPI creates a connection. As the presence of this directive impacts three separate MySQL charset settings which each have intricate effects based on their presense, SQLAlchemy will now emit the directive on new connections to ensure correct behavior. .. change:: :tags: usecase, postgresql :tickets: 4623 Added new dialect flag for the psycopg2 dialect, ``executemany_mode`` which supersedes the previous experimental ``use_batch_mode`` flag. ``executemany_mode`` supports both the "execute batch" and "execute values" functions provided by psycopg2, the latter which is used for compiled :func:`.insert` constructs. Pull request courtesy Yuval Dinari. .. seealso:: :ref:`psycopg2_executemany_mode` .. change:: :tags: bug, sql :tickets: 4787 Fixed bug where :meth:`.TypeEngine.column_expression` method would not be applied to subsequent SELECT statements inside of a UNION or other :class:`.CompoundSelect`, even though the SELECT statements are rendered at the topmost level of the statement. New logic now differentiates between rendering the column expression, which is needed for all SELECTs in the list, vs. gathering the returned data type for the result row, which is needed only for the first SELECT. .. change:: :tags: bug, sqlite :tickets: 4793 Fixed bug where usage of "PRAGMA table_info" in SQLite dialect meant that reflection features to detect for table existence, list of table columns, and list of foreign keys, would default to any table in any attached database, when no schema name was given and the table did not exist in the base schema. The fix explicitly runs PRAGMA for the 'main' schema and then the 'temp' schema if the 'main' returned no rows, to maintain the behavior of tables + temp tables in the "no schema" namespace, attached tables only in the "schema" namespace. .. change:: :tags: bug, sql :tickets: 4780 Fixed issue where internal cloning of SELECT constructs could lead to a key error if the copy of the SELECT changed its state such that its list of columns changed. This was observed to be occurring in some ORM scenarios which may be unique to 1.3 and above, so is partially a regression fix. .. change:: :tags: bug, orm :tickets: 4777 Fixed regression caused by new selectinload for many-to-one logic where a primaryjoin condition not based on real foreign keys would cause KeyError if a related object did not exist for a given key value on the parent object. .. change:: :tags: usecase, mysql :tickets: 4783 Added reserved words ARRAY and MEMBER to the MySQL reserved words list, as MySQL 8.0 has now made these reserved. .. change:: :tags: bug, events :tickets: 4794 Fixed issue in event system where using the ``once=True`` flag with dynamically generated listener functions would cause event registration of future events to fail if those listener functions were garbage collected after they were used, due to an assumption that a listened function is strongly referenced. The "once" wrapped is now modified to strongly reference the inner function persistently, and documentation is updated that using "once" does not imply automatic de-registration of listener functions. .. change:: :tags: bug, mysql :tickets: 4751 Added another fix for an upstream MySQL 8 issue where a case sensitive table name is reported incorrectly in foreign key constraint reflection, this is an extension of the fix first added for :ticket:`4344` which affects a case sensitive column name. The new issue occurs through MySQL 8.0.17, so the general logic of the 88718 fix remains in place. .. seealso:: https://bugs.mysql.com/bug.php?id=96365 - upstream bug .. change:: :tags: usecase, mssql :tickets: 4782 Added new :func:`.mssql.try_cast` construct for SQL Server which emits "TRY_CAST" syntax. Pull request courtesy Leonel Atencio. .. change:: :tags: bug, orm :tickets: 4803 Fixed bug where using :meth:`.Query.first` or a slice expression in conjunction with a query that has an expression based "offset" applied would raise TypeError, due to an "or" conditional against "offset" that did not expect it to be a SQL expression as opposed to an integer or None. .. changelog:: ```Links
- PyPI: https://pypi.org/project/sqlalchemy - Changelog: https://pyup.io/changelogs/sqlalchemy/ - Homepage: http://www.sqlalchemy.orgUpdate tqdm from 4.32.2 to 4.37.0.
Changelog
### 4.37.0 ``` - potential future pandas fix (824) - better unicode widechar support (803 -> 410, 805) - fix example/tqdm_wget unknown total (826) - add `stacklevel=2` to warnings (821) - misc framework updates + snapcraft version fix + update issue/pr templates (830) + update unit tests - misc documentation updates + update parallel (multiprocessing, ThreadPoolExecutor) example (407) + add slides, video images + add CII Best Practices badge + add repology badge + update badge icons ``` ### 4.36.1 ``` - fix CLI entrypoint ``` ### 4.36.0 ``` - expose more custom format params - potential thread safety fix (548) - update submodule architecture (198 -> 800) + backward-compatibility + expose `utils` + rename `main` -> `cli` + add/fix tests + fix minor cached var optimisation + `gui` partial upgrade (790) + `notebook` upgrade (790) * support `{bar}` in `bar_format` (594) * inherit methods including `set_*(refresh)` (740 -> 741) + ready for `contrib` releases (252) - support custom `bar_format` with unknown `total` - fix `tqdm_notebook` red block on explicit `file=None` (791) - update notebook to fully support custom `bar_format` (594, 649) - misc tidy + warnings + linting + update submodule contribution guide (252) + parallel `(py)make test` + fix Zenodo metadata - update documentation + `pandas`, `notebook`, `gui` (245) + indentation + update multiprocessing and multithreading examples (796) ``` ### 4.35.0 ``` - add `{bar}` format specifier (623 -> 799) + `[width][type]` - add tests and documentation - update performance tests ``` ### 4.34.0 ``` - add `leave=None` convenience option for `leave = position == 0` - ensure nested completed bars respect `leave=True` (230) - ensure nested bars are cleared before being moved up (795) - support both ` ` and `=` syntax for CLI options (761 -> 774) - misc documentation updates (778, 782) - fix/update tests - update GitHub docker package deployment ``` ### 4.33.0 ``` - fix `pandas==0.25` API change (780) - add contributor badges (`sourcerer`) - fix py26 travis CI - metadata fixes + `.zenodo.json` + `CODEOWNERS` - GitHub package registry docker deployment - minor linting - documentation updates (773) ```Links
- PyPI: https://pypi.org/project/tqdm - Changelog: https://pyup.io/changelogs/tqdm/ - Repo: https://github.com/tqdm/tqdmUpdate hypothesis from 4.32.2 to 4.42.5.
The bot wasn't able to find a changelog for this release. Got an idea?
Links
- PyPI: https://pypi.org/project/hypothesis - Changelog: https://pyup.io/changelogs/hypothesis/ - Repo: https://github.com/HypothesisWorks/hypothesis/tree/master/hypothesis-pythonUpdate pytest from 5.0.1 to 5.2.2.
Changelog
### 5.2.2 ``` ========================= Bug Fixes --------- - `5206 <https://github.com/pytest-dev/pytest/issues/5206>`_: Fix ``--nf`` to not forget about known nodeids with partial test selection. - `5906 <https://github.com/pytest-dev/pytest/issues/5906>`_: Fix crash with ``KeyboardInterrupt`` during ``--setup-show``. - `5946 <https://github.com/pytest-dev/pytest/issues/5946>`_: Fixed issue when parametrizing fixtures with numpy arrays (and possibly other sequence-like types). - `6044 <https://github.com/pytest-dev/pytest/issues/6044>`_: Properly ignore ``FileNotFoundError`` exceptions when trying to remove old temporary directories, for instance when multiple processes try to remove the same directory (common with ``pytest-xdist`` for example). ``` ### 5.2.1 ``` ========================= Bug Fixes --------- - `5902 <https://github.com/pytest-dev/pytest/issues/5902>`_: Fix warnings about deprecated ``cmp`` attribute in ``attrs>=19.2``. ``` ### 5.2.0 ``` ========================= Deprecations ------------ - `1682 <https://github.com/pytest-dev/pytest/issues/1682>`_: Passing arguments to pytest.fixture() as positional arguments is deprecated - pass them as a keyword argument instead. Features -------- - `1682 <https://github.com/pytest-dev/pytest/issues/1682>`_: The ``scope`` parameter of ``pytest.fixture`` can now be a callable that receives the fixture name and the ``config`` object as keyword-only parameters. See `the docs <https://docs.pytest.org/en/latest/fixture.htmldynamic-scope>`__ for more information. - `5764 <https://github.com/pytest-dev/pytest/issues/5764>`_: New behavior of the ``--pastebin`` option: failures to connect to the pastebin server are reported, without failing the pytest run Bug Fixes --------- - `5806 <https://github.com/pytest-dev/pytest/issues/5806>`_: Fix "lexer" being used when uploading to bpaste.net from ``--pastebin`` to "text". - `5884 <https://github.com/pytest-dev/pytest/issues/5884>`_: Fix ``--setup-only`` and ``--setup-show`` for custom pytest items. Trivial/Internal Changes ------------------------ - `5056 <https://github.com/pytest-dev/pytest/issues/5056>`_: The HelpFormatter uses ``py.io.get_terminal_width`` for better width detection. ``` ### 5.1.3 ``` ========================= Bug Fixes --------- - `5807 <https://github.com/pytest-dev/pytest/issues/5807>`_: Fix pypy3.6 (nightly) on windows. - `5811 <https://github.com/pytest-dev/pytest/issues/5811>`_: Handle ``--fulltrace`` correctly with ``pytest.raises``. - `5819 <https://github.com/pytest-dev/pytest/issues/5819>`_: Windows: Fix regression with conftest whose qualified name contains uppercase characters (introduced by 5792). ``` ### 5.1.2 ``` ========================= Bug Fixes --------- - `2270 <https://github.com/pytest-dev/pytest/issues/2270>`_: Fixed ``self`` reference in function-scoped fixtures defined plugin classes: previously ``self`` would be a reference to a *test* class, not the *plugin* class. - `570 <https://github.com/pytest-dev/pytest/issues/570>`_: Fixed long standing issue where fixture scope was not respected when indirect fixtures were used during parametrization. - `5782 <https://github.com/pytest-dev/pytest/issues/5782>`_: Fix decoding error when printing an error response from ``--pastebin``. - `5786 <https://github.com/pytest-dev/pytest/issues/5786>`_: Chained exceptions in test and collection reports are now correctly serialized, allowing plugins like ``pytest-xdist`` to display them properly. - `5792 <https://github.com/pytest-dev/pytest/issues/5792>`_: Windows: Fix error that occurs in certain circumstances when loading ``conftest.py`` from a working directory that has casing other than the one stored in the filesystem (e.g., ``c:\test`` instead of ``C:\test``). ``` ### 5.1.1 ``` ========================= Bug Fixes --------- - `5751 <https://github.com/pytest-dev/pytest/issues/5751>`_: Fixed ``TypeError`` when importing pytest on Python 3.5.0 and 3.5.1. ``` ### 5.1.0 ``` ========================= Removals -------- - `5180 <https://github.com/pytest-dev/pytest/issues/5180>`_: As per our policy, the following features have been deprecated in the 4.X series and are now removed: * ``Request.getfuncargvalue``: use ``Request.getfixturevalue`` instead. * ``pytest.raises`` and ``pytest.warns`` no longer support strings as the second argument. * ``message`` parameter of ``pytest.raises``. * ``pytest.raises``, ``pytest.warns`` and ``ParameterSet.param`` now use native keyword-only syntax. This might change the exception message from previous versions, but they still raise ``TypeError`` on unknown keyword arguments as before. * ``pytest.config`` global variable. * ``tmpdir_factory.ensuretemp`` method. * ``pytest_logwarning`` hook. * ``RemovedInPytest4Warning`` warning type. * ``request`` is now a reserved name for fixtures. For more information consult `Deprecations and Removals <https://docs.pytest.org/en/latest/deprecations.html>`__ in the docs. - `5565 <https://github.com/pytest-dev/pytest/issues/5565>`_: Removed unused support code for `unittest2 <https://pypi.org/project/unittest2/>`__. The ``unittest2`` backport module is no longer necessary since Python 3.3+, and the small amount of code in pytest to support it also doesn't seem to be used: after removed, all tests still pass unchanged. Although our policy is to introduce a deprecation period before removing any features or support for third party libraries, because this code is apparently not used at all (even if ``unittest2`` is used by a test suite executed by pytest), it was decided to remove it in this release. If you experience a regression because of this, please `file an issue <https://github.com/pytest-dev/pytest/issues/new>`__. - `5615 <https://github.com/pytest-dev/pytest/issues/5615>`_: ``pytest.fail``, ``pytest.xfail`` and ``pytest.skip`` no longer support bytes for the message argument. This was supported for Python 2 where it was tempting to use ``"message"`` instead of ``u"message"``. Python 3 code is unlikely to pass ``bytes`` to these functions. If you do, please decode it to an ``str`` beforehand. Features -------- - `5564 <https://github.com/pytest-dev/pytest/issues/5564>`_: New ``Config.invocation_args`` attribute containing the unchanged arguments passed to ``pytest.main()``. - `5576 <https://github.com/pytest-dev/pytest/issues/5576>`_: New `NUMBER <https://docs.pytest.org/en/latest/doctest.htmlusing-doctest-options>`__ option for doctests to ignore irrelevant differences in floating-point numbers. Inspired by Sébastien Boisgérault's `numtest <https://github.com/boisgera/numtest>`__ extension for doctest. Improvements ------------ - `5471 <https://github.com/pytest-dev/pytest/issues/5471>`_: JUnit XML now includes a timestamp and hostname in the testsuite tag. - `5707 <https://github.com/pytest-dev/pytest/issues/5707>`_: Time taken to run the test suite now includes a human-readable representation when it takes over 60 seconds, for example:: ===== 2 failed in 102.70s (0:01:42) ===== Bug Fixes --------- - `4344 <https://github.com/pytest-dev/pytest/issues/4344>`_: Fix RuntimeError/StopIteration when trying to collect package with "__init__.py" only. - `5115 <https://github.com/pytest-dev/pytest/issues/5115>`_: Warnings issued during ``pytest_configure`` are explicitly not treated as errors, even if configured as such, because it otherwise completely breaks pytest. - `5477 <https://github.com/pytest-dev/pytest/issues/5477>`_: The XML file produced by ``--junitxml`` now correctly contain a ``<testsuites>`` root element. - `5524 <https://github.com/pytest-dev/pytest/issues/5524>`_: Fix issue where ``tmp_path`` and ``tmpdir`` would not remove directories containing files marked as read-only, which could lead to pytest crashing when executed a second time with the ``--basetemp`` option. - `5537 <https://github.com/pytest-dev/pytest/issues/5537>`_: Replace ``importlib_metadata`` backport with ``importlib.metadata`` from the standard library on Python 3.8+. - `5578 <https://github.com/pytest-dev/pytest/issues/5578>`_: Improve type checking for some exception-raising functions (``pytest.xfail``, ``pytest.skip``, etc) so they provide better error messages when users meant to use marks (for example ``pytest.xfail`` instead of ``pytest.mark.xfail``). - `5606 <https://github.com/pytest-dev/pytest/issues/5606>`_: Fixed internal error when test functions were patched with objects that cannot be compared for truth values against others, like ``numpy`` arrays. - `5634 <https://github.com/pytest-dev/pytest/issues/5634>`_: ``pytest.exit`` is now correctly handled in ``unittest`` cases. This makes ``unittest`` cases handle ``quit`` from pytest's pdb correctly. - `5650 <https://github.com/pytest-dev/pytest/issues/5650>`_: Improved output when parsing an ini configuration file fails. - `5701 <https://github.com/pytest-dev/pytest/issues/5701>`_: Fix collection of ``staticmethod`` objects defined with ``functools.partial``. - `5734 <https://github.com/pytest-dev/pytest/issues/5734>`_: Skip async generator test functions, and update the warning message to refer to ``async def`` functions. Improved Documentation ---------------------- - `5669 <https://github.com/pytest-dev/pytest/issues/5669>`_: Add docstring for ``Testdir.copy_example``. Trivial/Internal Changes ------------------------ - `5095 <https://github.com/pytest-dev/pytest/issues/5095>`_: XML files of the ``xunit2`` family are now validated against the schema by pytest's own test suite to avoid future regressions. - `5516 <https://github.com/pytest-dev/pytest/issues/5516>`_: Cache node splitting function which can improve collection performance in very large test suites. - `5603 <https://github.com/pytest-dev/pytest/issues/5603>`_: Simplified internal ``SafeRepr`` class and removed some dead code. - `5664 <https://github.com/pytest-dev/pytest/issues/5664>`_: When invoking pytest's own testsuite with ``PYTHONDONTWRITEBYTECODE=1``, the ``test_xfail_handling`` test no longer fails. - `5684 <https://github.com/pytest-dev/pytest/issues/5684>`_: Replace manual handling of ``OSError.errno`` in the codebase by new ``OSError`` subclasses (``PermissionError``, ``FileNotFoundError``, etc.). ```Links
- PyPI: https://pypi.org/project/pytest - Changelog: https://pyup.io/changelogs/pytest/ - Homepage: https://docs.pytest.org/en/latest/Update pytest-cov from 2.7.1 to 2.8.1.
Changelog
### 2.8.1 ``` ------------------ * Fixed `348 <https://github.com/pytest-dev/pytest-cov/issues/348>`_ - regression when only certain reports (html or xml) are used then ``--cov-fail-under`` always fails. ``` ### 2.8.0 ``` ------------------ * Fixed ``RecursionError`` that can occur when using `cleanup_on_signal <https://pytest-cov.readthedocs.io/en/latest/subprocess-support.htmlif-you-got-custom-signal-handling>`__ or `cleanup_on_sigterm <https://pytest-cov.readthedocs.io/en/latest/subprocess-support.htmlif-you-got-custom-signal-handling>`__. See: `294 <https://github.com/pytest-dev/pytest-cov/issues/294>`_. The 2.7.x releases of pytest-cov should be considered broken regarding aforementioned cleanup API. * Added compatibility with future xdist release that deprecates some internals (match pytest-xdist master/worker terminology). Contributed by Thomas Grainger in `321 <https://github.com/pytest-dev/pytest-cov/pull/321>`_ * Fixed breakage that occurs when multiple reporting options are used. Contributed by Thomas Grainger in `338 <https://github.com/pytest-dev/pytest-cov/pull/338>`_. * Changed internals to use a stub instead of ``os.devnull``. Contributed by Thomas Grainger in `332 <https://github.com/pytest-dev/pytest-cov/pull/332>`_. * Added support for Coverage 5.0. Contributed by Ned Batchelder in `319 <https://github.com/pytest-dev/pytest-cov/pull/319>`_. * Added support for float values in ``--cov-fail-under``. Contributed by Martín Gaitán in `311 <https://github.com/pytest-dev/pytest-cov/pull/311>`_. * Various documentation fixes. Contributed by Juanjo Bazán, Andrew Murray and Albert Tugushev in `298 <https://github.com/pytest-dev/pytest-cov/pull/298>`_, `299 <https://github.com/pytest-dev/pytest-cov/pull/299>`_ and `307 <https://github.com/pytest-dev/pytest-cov/pull/307>`_. * Various testing improvements. Contributed by Ned Batchelder, Daniel Hahler, Ionel Cristian Mărieș and Hugo van Kemenade in `313 <https://github.com/pytest-dev/pytest-cov/pull/313>`_, `314 <https://github.com/pytest-dev/pytest-cov/pull/314>`_, `315 <https://github.com/pytest-dev/pytest-cov/pull/315>`_, `316 <https://github.com/pytest-dev/pytest-cov/pull/316>`_, `325 <https://github.com/pytest-dev/pytest-cov/pull/325>`_, `326 <https://github.com/pytest-dev/pytest-cov/pull/326>`_, `334 <https://github.com/pytest-dev/pytest-cov/pull/334>`_ and `335 <https://github.com/pytest-dev/pytest-cov/pull/335>`_. * Added the ``--cov-context`` CLI options that enables coverage contexts. Only works with coverage 5.0+. Contributed by Ned Batchelder in `345 <https://github.com/pytest-dev/pytest-cov/pull/345>`_. ```Links
- PyPI: https://pypi.org/project/pytest-cov - Changelog: https://pyup.io/changelogs/pytest-cov/ - Repo: https://github.com/pytest-dev/pytest-covUpdate python-coveralls from 2.9.2 to 2.9.3.
The bot wasn't able to find a changelog for this release. Got an idea?
Links
- PyPI: https://pypi.org/project/python-coveralls - Changelog: https://pyup.io/changelogs/python-coveralls/ - Repo: http://github.com/z4r/python-coveralls