Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Scheduled biweekly dependency update for week 27 #710

Closed
wants to merge 46 commits into from

Conversation

pyup-bot
Copy link
Collaborator

@pyup-bot pyup-bot commented Jul 3, 2023

Update numpy from 1.24.2 to 1.25.0.

Changelog

1.25.0

The NumPy 1.25.0 release continues the ongoing work to improve the
handling and promotion of dtypes, increase the execution speed, and
clarify the documentation. There has also been work to prepare for the
future NumPy 2.0.0 release, resulting in a large number of new and
expired deprecation. Highlights are:

-   Support for MUSL, there are now MUSL wheels.
-   Support the Fujitsu C/C++ compiler.
-   Object arrays are now supported in einsum
-   Support for inplace matrix multiplication (`=`).

We will be releasing a NumPy 1.26 when Python 3.12 comes out. That is
needed because distutils has been dropped by Python 3.12 and we will be
switching to using meson for future builds. The next mainline release
will be NumPy 2.0.0. We plan that the 2.0 series will still support
downstream projects built against earlier versions of NumPy.

The Python versions supported in this release are 3.9-3.11.

Deprecations

-   `np.core.MachAr` is deprecated. It is private API. In names defined
 in `np.core` should generally be considered private.

 ([gh-22638](https://github.com/numpy/numpy/pull/22638))

-   `np.finfo(None)` is deprecated.

 ([gh-23011](https://github.com/numpy/numpy/pull/23011))

-   `np.round_` is deprecated. Use `np.round` instead.

 ([gh-23302](https://github.com/numpy/numpy/pull/23302))

-   `np.product` is deprecated. Use `np.prod` instead.

 ([gh-23314](https://github.com/numpy/numpy/pull/23314))

-   `np.cumproduct` is deprecated. Use `np.cumprod` instead.

 ([gh-23314](https://github.com/numpy/numpy/pull/23314))

-   `np.sometrue` is deprecated. Use `np.any` instead.

 ([gh-23314](https://github.com/numpy/numpy/pull/23314))

-   `np.alltrue` is deprecated. Use `np.all` instead.

 ([gh-23314](https://github.com/numpy/numpy/pull/23314))

-   Only ndim-0 arrays are treated as scalars. NumPy used to treat all
 arrays of size 1 (e.g., `np.array([3.14])`) as scalars. In the
 future, this will be limited to arrays of ndim 0 (e.g.,
 `np.array(3.14)`). The following expressions will report a
 deprecation warning:

  python
 a = np.array([3.14])
 float(a)   better: a[0] to get the numpy.float or a.item()

 b = np.array([[3.14]])
 c = numpy.random.rand(10)
 c[0] = b   better: c[0] = b[0, 0]
 

 ([gh-10615](https://github.com/numpy/numpy/pull/10615))

-   `numpy.find_common_type` is now deprecated and its use
 should be replaced with either `numpy.result_type` or
 `numpy.promote_types`. Most users leave the second
 `scalar_types` argument to `find_common_type` as `[]` in which case
 `np.result_type` and `np.promote_types` are both faster and more
 robust. When not using `scalar_types` the main difference is that
 the replacement intentionally converts non-native byte-order to
 native byte order. Further, `find_common_type` returns `object`
 dtype rather than failing promotion. This leads to differences when
 the inputs are not all numeric. Importantly, this also happens for
 e.g. timedelta/datetime for which NumPy promotion rules are
 currently sometimes surprising.

 When the `scalar_types` argument is not `[]` things are more
 complicated. In most cases, using `np.result_type` and passing the
 Python values `0`, `0.0`, or `0j` has the same result as using
 `int`, `float`, or `complex` in `scalar_types`.

 When `scalar_types` is constructed, `np.result_type` is the correct
 replacement and it may be passed scalar values like
 `np.float32(0.0)`. Passing values other than 0, may lead to
 value-inspecting behavior (which `np.find_common_type` never used
 and NEP 50 may change in the future). The main possible change in
 behavior in this case, is when the array types are signed integers
 and scalar types are unsigned.

 If you are unsure about how to replace a use of `scalar_types` or
 when non-numeric dtypes are likely, please do not hesitate to open a
 NumPy issue to ask for help.

 ([gh-22539](https://github.com/numpy/numpy/pull/22539))

Expired deprecations

-   `np.core.machar` and `np.finfo.machar` have been removed.

 ([gh-22638](https://github.com/numpy/numpy/pull/22638))

-   `+arr` will now raise an error when the dtype is not numeric (and
 positive is undefined).

 ([gh-22998](https://github.com/numpy/numpy/pull/22998))

-   A sequence must now be passed into the stacking family of functions
 (`stack`, `vstack`, `hstack`, `dstack` and `column_stack`).

 ([gh-23019](https://github.com/numpy/numpy/pull/23019))

-   `np.clip` now defaults to same-kind casting. Falling back to unsafe
 casting was deprecated in NumPy 1.17.

 ([gh-23403](https://github.com/numpy/numpy/pull/23403))

-   `np.clip` will now propagate `np.nan` values passed as `min` or
 `max`. Previously, a scalar NaN was usually ignored. This was
 deprecated in NumPy 1.17.

 ([gh-23403](https://github.com/numpy/numpy/pull/23403))

-   The `np.dual` submodule has been removed.

 ([gh-23480](https://github.com/numpy/numpy/pull/23480))

-   NumPy now always ignores sequence behavior for an array-like
 (defining one of the array protocols). (Deprecation started NumPy
 1.20)

 ([gh-23660](https://github.com/numpy/numpy/pull/23660))

-   The niche `FutureWarning` when casting to a subarray dtype in
 `astype` or the array creation functions such as `asarray` is now
 finalized. The behavior is now always the same as if the subarray
 dtype was wrapped into a single field (which was the workaround,
 previously). (FutureWarning since NumPy 1.20)

 ([gh-23666](https://github.com/numpy/numpy/pull/23666))

-   `==` and `!=` warnings have been finalized. The `==` and `!=`
 operators on arrays now always:

 -   raise errors that occur during comparisons such as when the
     arrays have incompatible shapes
     (`np.array([1, 2]) == np.array([1, 2, 3])`).

 -   return an array of all `True` or all `False` when values are
     fundamentally not comparable (e.g. have different dtypes). An
     example is `np.array(["a"]) == np.array([1])`.

     This mimics the Python behavior of returning `False` and `True`
     when comparing incompatible types like `"a" == 1` and
     `"a" != 1`. For a long time these gave `DeprecationWarning` or
     `FutureWarning`.

 ([gh-22707](https://github.com/numpy/numpy/pull/22707))

-   Nose support has been removed. NumPy switched to using pytest in
 2018 and nose has been unmaintained for many years. We have kept
 NumPy\'s nose support to avoid breaking downstream projects who
 might have been using it and not yet switched to pytest or some
 other testing framework. With the arrival of Python 3.12, unpatched
 nose will raise an error. It is time to move on.

 *Decorators removed*:

 -   raises
 -   slow
 -   setastest
 -   skipif
 -   knownfailif
 -   deprecated
 -   parametrize
 -   \_needs_refcount

 These are not to be confused with pytest versions with similar
 names, e.g., pytest.mark.slow, pytest.mark.skipif,
 pytest.mark.parametrize.

 *Functions removed*:

 -   Tester
 -   import_nose
 -   run_module_suite

 ([gh-23041](https://github.com/numpy/numpy/pull/23041))

-   The `numpy.testing.utils` shim has been removed. Importing from the
 `numpy.testing.utils` shim has been deprecated since 2019, the shim
 has now been removed. All imports should be made directly from
 `numpy.testing`.

 ([gh-23060](https://github.com/numpy/numpy/pull/23060))

-   The environment variable to disable dispatching has been removed.
 Support for the `NUMPY_EXPERIMENTAL_ARRAY_FUNCTION` environment
 variable has been removed. This variable disabled dispatching with
 `__array_function__`.

 ([gh-23376](https://github.com/numpy/numpy/pull/23376))

-   Support for `y=` as an alias of `out=` has been removed. The `fix`,
 `isposinf` and `isneginf` functions allowed using `y=` as a
 (deprecated) alias for `out=`. This is no longer supported.

 ([gh-23376](https://github.com/numpy/numpy/pull/23376))

Compatibility notes

-   The `busday_count` method now correctly handles cases where the
 `begindates` is later in time than the `enddates`. Previously, the
 `enddates` was included, even though the documentation states it is
 always excluded.

 ([gh-23229](https://github.com/numpy/numpy/pull/23229))

-   When comparing datetimes and timedelta using `np.equal` or
 `np.not_equal` numpy previously allowed the comparison with
 `casting="unsafe"`. This operation now fails. Forcing the output
 dtype using the `dtype` kwarg can make the operation succeed, but we
 do not recommend it.

 ([gh-22707](https://github.com/numpy/numpy/pull/22707))

-   When loading data from a file handle using `np.load`, if the handle
 is at the end of file, as can happen when reading multiple arrays by
 calling `np.load` repeatedly, numpy previously raised `ValueError`
 if `allow_pickle=False`, and `OSError` if `allow_pickle=True`. Now
 it raises `EOFError` instead, in both cases.

 ([gh-23105](https://github.com/numpy/numpy/pull/23105))

`np.pad` with `mode=wrap` pads with strict multiples of original data

Code based on earlier version of `pad` that uses `mode="wrap"` will
return different results when the padding size is larger than initial
array.

`np.pad` with `mode=wrap` now always fills the space with strict
multiples of original data even if the padding size is larger than the
initial array.

([gh-22575](https://github.com/numpy/numpy/pull/22575))

Cython `long_t` and `ulong_t` removed

`long_t` and `ulong_t` were aliases for `longlong_t` and `ulonglong_t`
and confusing (a remainder from of Python 2). This change may lead to
the errors:

 'long_t' is not a type identifier
 'ulong_t' is not a type identifier

We recommend use of bit-sized types such as `cnp.int64_t` or the use of
`cnp.intp_t` which is 32 bits on 32 bit systems and 64 bits on 64 bit
systems (this is most compatible with indexing). If C `long` is desired,
use plain `long` or `npy_long`. `cnp.int_t` is also `long` (NumPy\'s
default integer). However, `long` is 32 bit on 64 bit windows and we may
wish to adjust this even in NumPy. (Please do not hesitate to contact
NumPy developers if you are curious about this.)

([gh-22637](https://github.com/numpy/numpy/pull/22637))

Changed error message and type for bad `axes` argument to `ufunc`

The error message and type when a wrong `axes` value is passed to
`ufunc(..., axes=[...])` has changed. The message is now more
indicative of the problem, and if the value is mismatched an
`AxisError` will be raised. A `TypeError` will still be raised for
invalidinput types.

([gh-22675](https://github.com/numpy/numpy/pull/22675))

Array-likes that define `__array_ufunc__` can now override ufuncs if used as `where`

If the `where` keyword argument of a `numpy.ufunc`{.interpreted-text
role="class"} is a subclass of `numpy.ndarray`{.interpreted-text
role="class"} or is a duck type that defines
`numpy.class.__array_ufunc__`{.interpreted-text role="func"} it can
override the behavior of the ufunc using the same mechanism as the input
and output arguments. Note that for this to work properly, the
`where.__array_ufunc__` implementation will have to unwrap the `where`
argument to pass it into the default implementation of the `ufunc` or,
for `numpy.ndarray`{.interpreted-text role="class"} subclasses before
using `super().__array_ufunc__`.

([gh-23240](https://github.com/numpy/numpy/pull/23240))

Compiling against the NumPy C API is now backwards compatible by default

NumPy now defaults to exposing a backwards compatible subset of the
C-API. This makes the use of `oldest-supported-numpy` unnecessary.
Libraries can override the default minimal version to be compatible with
using:

 define NPY_TARGET_VERSION NPY_1_22_API_VERSION

before including NumPy or by passing the equivalent `-D` option to the
compiler. The NumPy 1.25 default is `NPY_1_19_API_VERSION`. Because the

1.24.4

discovered after the 1.24.3 release. It is the last planned
release in the 1.24.x cycle. The Python versions supported by
this release are 3.8-3.11.

Contributors

A total of 4 people contributed to this release. People with a \"+\" by
their names contributed a patch for the first time.

-   Bas van Beek
-   Charles Harris
-   Sebastian Berg
-   Hongyang Peng +

Pull requests merged

A total of 6 pull requests were merged for this release.

-   [23720](https://github.com/numpy/numpy/pull/23720): MAINT, BLD: Pin rtools to version 4.0 for Windows builds.
-   [23739](https://github.com/numpy/numpy/pull/23739): BUG: fix the method for checking local files for 1.24.x
-   [23760](https://github.com/numpy/numpy/pull/23760): MAINT: Copy rtools installation from install-rtools.
-   [23761](https://github.com/numpy/numpy/pull/23761): BUG: Fix masked array ravel order for A (and somewhat K)
-   [23890](https://github.com/numpy/numpy/pull/23890): TYP,DOC: Annotate and document the `metadata` parameter of\...
-   [23994](https://github.com/numpy/numpy/pull/23994): MAINT: Update rtools installation

Checksums

MD5

 25049e3aee79dde29e7a498d3ad13379  numpy-1.24.4-cp310-cp310-macosx_10_9_x86_64.whl
 579b5c357c918feaef4af03af8afb721  numpy-1.24.4-cp310-cp310-macosx_11_0_arm64.whl
 c873a14fa4f0210884db9c05e2904286  numpy-1.24.4-cp310-cp310-manylinux_2_17_aarch64.manylinux2014_aarch64.whl
 110a13ac016286059f0658b52b3646c0  numpy-1.24.4-cp310-cp310-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
 fa67218966c0aef4094867cad7703648  numpy-1.24.4-cp310-cp310-win32.whl
 6ee768803d8ebac43ee0a04e628a69f9  numpy-1.24.4-cp310-cp310-win_amd64.whl
 0c918c16b58cb7f6773ea7d76e0bdaff  numpy-1.24.4-cp311-cp311-macosx_10_9_x86_64.whl
 20506ae8003faf097c6b3a8915b4140e  numpy-1.24.4-cp311-cp311-macosx_11_0_arm64.whl
 902df9d5963e89d88a1939d94207857f  numpy-1.24.4-cp311-cp311-manylinux_2_17_aarch64.manylinux2014_aarch64.whl
 2543611d802c141c8276e4868b4d9619  numpy-1.24.4-cp311-cp311-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
 37b23a4e4e148d61dd3a515ac5dbf7ec  numpy-1.24.4-cp311-cp311-win32.whl
 25e9f6bee2b65ff2a87588e717f15165  numpy-1.24.4-cp311-cp311-win_amd64.whl
 f39a0cc3655a482af7d300bcaff5978e  numpy-1.24.4-cp38-cp38-macosx_10_9_x86_64.whl
 9ed27941388fdb392e8969169f3fc600  numpy-1.24.4-cp38-cp38-macosx_11_0_arm64.whl
 dee3f0c7482f1dc8bd1cd27b9b028a2c  numpy-1.24.4-cp38-cp38-manylinux_2_17_aarch64.manylinux2014_aarch64.whl
 2cc0967af29df3caef9fb3520f14e071  numpy-1.24.4-cp38-cp38-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
 8572a3a0973fa78355bcb5f737745b47  numpy-1.24.4-cp38-cp38-win32.whl
 771c63f2ef0d31466bbb12362a532265  numpy-1.24.4-cp38-cp38-win_amd64.whl
 5713d9dc3dff287fb72121fe1960c48d  numpy-1.24.4-cp39-cp39-macosx_10_9_x86_64.whl
 4e6718e3b655219a2a733b4fa242ca32  numpy-1.24.4-cp39-cp39-macosx_11_0_arm64.whl
 31487f9a52ef81f8f88ec7fce8738dad  numpy-1.24.4-cp39-cp39-manylinux_2_17_aarch64.manylinux2014_aarch64.whl
 ea597b30187e55eb16ee31631e66f60d  numpy-1.24.4-cp39-cp39-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
 98adbf30c67154056474001c125f6188  numpy-1.24.4-cp39-cp39-win32.whl
 49c444b0e572ef45f1d92c106a36004e  numpy-1.24.4-cp39-cp39-win_amd64.whl
 cdddfdeac437b0f20b4e366f00b5c42e  numpy-1.24.4-pp38-pypy38_pp73-macosx_10_9_x86_64.whl
 3778338c15628caa3abd61e6f7bd46ec  numpy-1.24.4-pp38-pypy38_pp73-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
 e16bd49d5295dc1b01ed50d76229fb54  numpy-1.24.4-pp38-pypy38_pp73-win_amd64.whl
 3f3995540a17854a29dc79f8eeecd832  numpy-1.24.4.tar.gz

SHA256

 c0bfb52d2169d58c1cdb8cc1f16989101639b34c7d3ce60ed70b19c63eba0b64  numpy-1.24.4-cp310-cp310-macosx_10_9_x86_64.whl
 ed094d4f0c177b1b8e7aa9cba7d6ceed51c0e569a5318ac0ca9a090680a6a1b1  numpy-1.24.4-cp310-cp310-macosx_11_0_arm64.whl
 79fc682a374c4a8ed08b331bef9c5f582585d1048fa6d80bc6c35bc384eee9b4  numpy-1.24.4-cp310-cp310-manylinux_2_17_aarch64.manylinux2014_aarch64.whl
 7ffe43c74893dbf38c2b0a1f5428760a1a9c98285553c89e12d70a96a7f3a4d6  numpy-1.24.4-cp310-cp310-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
 4c21decb6ea94057331e111a5bed9a79d335658c27ce2adb580fb4d54f2ad9bc  numpy-1.24.4-cp310-cp310-win32.whl
 b4bea75e47d9586d31e892a7401f76e909712a0fd510f58f5337bea9572c571e  numpy-1.24.4-cp310-cp310-win_amd64.whl
 f136bab9c2cfd8da131132c2cf6cc27331dd6fae65f95f69dcd4ae3c3639c810  numpy-1.24.4-cp311-cp311-macosx_10_9_x86_64.whl
 e2926dac25b313635e4d6cf4dc4e51c8c0ebfed60b801c799ffc4c32bf3d1254  numpy-1.24.4-cp311-cp311-macosx_11_0_arm64.whl
 222e40d0e2548690405b0b3c7b21d1169117391c2e82c378467ef9ab4c8f0da7  numpy-1.24.4-cp311-cp311-manylinux_2_17_aarch64.manylinux2014_aarch64.whl
 7215847ce88a85ce39baf9e89070cb860c98fdddacbaa6c0da3ffb31b3350bd5  numpy-1.24.4-cp311-cp311-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
 4979217d7de511a8d57f4b4b5b2b965f707768440c17cb70fbf254c4b225238d  numpy-1.24.4-cp311-cp311-win32.whl
 b7b1fc9864d7d39e28f41d089bfd6353cb5f27ecd9905348c24187a768c79694  numpy-1.24.4-cp311-cp311-win_amd64.whl
 1452241c290f3e2a312c137a9999cdbf63f78864d63c79039bda65ee86943f61  numpy-1.24.4-cp38-cp38-macosx_10_9_x86_64.whl
 04640dab83f7c6c85abf9cd729c5b65f1ebd0ccf9de90b270cd61935eef0197f  numpy-1.24.4-cp38-cp38-macosx_11_0_arm64.whl
 a5425b114831d1e77e4b5d812b69d11d962e104095a5b9c3b641a218abcc050e  numpy-1.24.4-cp38-cp38-manylinux_2_17_aarch64.manylinux2014_aarch64.whl
 dd80e219fd4c71fc3699fc1dadac5dcf4fd882bfc6f7ec53d30fa197b8ee22dc  numpy-1.24.4-cp38-cp38-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
 4602244f345453db537be5314d3983dbf5834a9701b7723ec28923e2889e0bb2  numpy-1.24.4-cp38-cp38-win32.whl
 692f2e0f55794943c5bfff12b3f56f99af76f902fc47487bdfe97856de51a706  numpy-1.24.4-cp38-cp38-win_amd64.whl
 2541312fbf09977f3b3ad449c4e5f4bb55d0dbf79226d7724211acc905049400  numpy-1.24.4-cp39-cp39-macosx_10_9_x86_64.whl
 9667575fb6d13c95f1b36aca12c5ee3356bf001b714fc354eb5465ce1609e62f  numpy-1.24.4-cp39-cp39-macosx_11_0_arm64.whl
 f3a86ed21e4f87050382c7bc96571755193c4c1392490744ac73d660e8f564a9  numpy-1.24.4-cp39-cp39-manylinux_2_17_aarch64.manylinux2014_aarch64.whl
 d11efb4dbecbdf22508d55e48d9c8384db795e1b7b51ea735289ff96613ff74d  numpy-1.24.4-cp39-cp39-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
 6620c0acd41dbcb368610bb2f4d83145674040025e5536954782467100aa8835  numpy-1.24.4-cp39-cp39-win32.whl
 befe2bf740fd8373cf56149a5c23a0f601e82869598d41f8e188a0e9869926f8  numpy-1.24.4-cp39-cp39-win_amd64.whl
 31f13e25b4e304632a4619d0e0777662c2ffea99fcae2029556b17d8ff958aef  numpy-1.24.4-pp38-pypy38_pp73-macosx_10_9_x86_64.whl
 95f7ac6540e95bc440ad77f56e520da5bf877f87dca58bd095288dce8940532a  numpy-1.24.4-pp38-pypy38_pp73-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
 e98f220aa76ca2a977fe435f5b04d7b3470c0a2e6312907b37ba6068f26787f2  numpy-1.24.4-pp38-pypy38_pp73-win_amd64.whl
 80f5e3a4e498641401868df4208b74581206afbee7cf7b8329daae82676d9463  numpy-1.24.4.tar.gz

1.24.3

discovered after the 1.24.2 release. The Python versions supported by
this release are 3.8-3.11.

Contributors

A total of 12 people contributed to this release. People with a \"+\" by
their names contributed a patch for the first time.

-   Aleksei Nikiforov +
-   Alexander Heger
-   Bas van Beek
-   Bob Eldering
-   Brock Mendel
-   Charles Harris
-   Kyle Sunden
-   Peter Hawkins
-   Rohit Goswami
-   Sebastian Berg
-   Warren Weckesser
-   dependabot\[bot\]

Pull requests merged

A total of 17 pull requests were merged for this release.

-   [23206](https://github.com/numpy/numpy/pull/23206): BUG: fix for f2py string scalars (#23194)
-   [23207](https://github.com/numpy/numpy/pull/23207): BUG: datetime64/timedelta64 comparisons return NotImplemented
-   [23208](https://github.com/numpy/numpy/pull/23208): MAINT: Pin matplotlib to version 3.6.3 for refguide checks
-   [23221](https://github.com/numpy/numpy/pull/23221): DOC: Fix matplotlib error in documentation
-   [23226](https://github.com/numpy/numpy/pull/23226): CI: Ensure submodules are initialized in gitpod.
-   [23341](https://github.com/numpy/numpy/pull/23341): TYP: Replace duplicate reduce in ufunc type signature with reduceat.
-   [23342](https://github.com/numpy/numpy/pull/23342): TYP: Remove duplicate CLIP/WRAP/RAISE in `__init__.pyi`.
-   [23343](https://github.com/numpy/numpy/pull/23343): TYP: Mark `d` argument to fftfreq and rfftfreq as optional\...
-   [23344](https://github.com/numpy/numpy/pull/23344): TYP: Add type annotations for comparison operators to MaskedArray.
-   [23345](https://github.com/numpy/numpy/pull/23345): TYP: Remove some stray type-check-only imports of `msort`
-   [23370](https://github.com/numpy/numpy/pull/23370): BUG: Ensure like is only stripped for `like=` dispatched functions
-   [23543](https://github.com/numpy/numpy/pull/23543): BUG: fix loading and storing big arrays on s390x
-   [23544](https://github.com/numpy/numpy/pull/23544): MAINT: Bump larsoner/circleci-artifacts-redirector-action
-   [23634](https://github.com/numpy/numpy/pull/23634): BUG: Ignore invalid and overflow warnings in masked setitem
-   [23635](https://github.com/numpy/numpy/pull/23635): BUG: Fix masked array raveling when `order="A"` or `order="K"`
-   [23636](https://github.com/numpy/numpy/pull/23636): MAINT: Update conftest for newer hypothesis versions
-   [23637](https://github.com/numpy/numpy/pull/23637): BUG: Fix bug in parsing F77 style string arrays.

Checksums

MD5

 93a3ce07e3773842c54d831f18e3eb8d  numpy-1.24.3-cp310-cp310-macosx_10_9_x86_64.whl
 39691ff3d1612438dfcd3266c9765aab  numpy-1.24.3-cp310-cp310-macosx_11_0_arm64.whl
 a99234799a239e7e9c6fa15c212996df  numpy-1.24.3-cp310-cp310-manylinux_2_17_aarch64.manylinux2014_aarch64.whl
 3673aa638746851dd19d5199e1eb3a91  numpy-1.24.3-cp310-cp310-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
 3c72962360bcd0938a6bddee6cdca766  numpy-1.24.3-cp310-cp310-win32.whl
 a3329efa646012fa4ee06ce5e08eadaf  numpy-1.24.3-cp310-cp310-win_amd64.whl
 5323fb0323d1ec10ee3c35a2fa79cbcd  numpy-1.24.3-cp311-cp311-macosx_10_9_x86_64.whl
 cfa001dcd07cdf6414ced433e88959d4  numpy-1.24.3-cp311-cp311-macosx_11_0_arm64.whl
 d75bbfb06ed00d04232dce0e865eb42c  numpy-1.24.3-cp311-cp311-manylinux_2_17_aarch64.manylinux2014_aarch64.whl
 fe18b810bcf284572467ce585dbc533b  numpy-1.24.3-cp311-cp311-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
 e97699a4ef96a81e0916bdf15440abe0  numpy-1.24.3-cp311-cp311-win32.whl
 e6de5b7d77dc43ed47f516eb10bbe8b6  numpy-1.24.3-cp311-cp311-win_amd64.whl
 dd04ebf441a8913f4900b56e7a33a75e  numpy-1.24.3-cp38-cp38-macosx_10_9_x86_64.whl
 e47ac5521b0bfc3effb040072d8a7902  numpy-1.24.3-cp38-cp38-macosx_11_0_arm64.whl
 7b7dae3309e7ca8a8859633a5d337431  numpy-1.24.3-cp38-cp38-manylinux_2_17_aarch64.manylinux2014_aarch64.whl
 8cc87b88163ed84e70c48fd0f5f8f20e  numpy-1.24.3-cp38-cp38-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
 350934bae971d0ebe231a59b640069db  numpy-1.24.3-cp38-cp38-win32.whl
 c4708ef009bb5d427ea94a4fc4a10e12  numpy-1.24.3-cp38-cp38-win_amd64.whl
 44b08a293a4e12d62c27b8f15ba5664e  numpy-1.24.3-cp39-cp39-macosx_10_9_x86_64.whl
 3ae7ac30f86c720e42b2324a0ae1adf5  numpy-1.24.3-cp39-cp39-macosx_11_0_arm64.whl
 065464a8d918c670c7863d1e72e3e6dd  numpy-1.24.3-cp39-cp39-manylinux_2_17_aarch64.manylinux2014_aarch64.whl
 1f163b9ea417c253e84480aa8d99dee6  numpy-1.24.3-cp39-cp39-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
 c86e648389e333e062bea11c749b9a32  numpy-1.24.3-cp39-cp39-win32.whl
 bfe332e577c604d6d62a57381e6aa0a6  numpy-1.24.3-cp39-cp39-win_amd64.whl
 374695eeef5aca32a5b7f2f518dd3ba1  numpy-1.24.3-pp38-pypy38_pp73-macosx_10_9_x86_64.whl
 6abd9dba54405182e6e7bb32dbe377bb  numpy-1.24.3-pp38-pypy38_pp73-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
 0848bd41c08dd5ebbc5a7f0788678e0e  numpy-1.24.3-pp38-pypy38_pp73-win_amd64.whl
 89e5e2e78407032290ae6acf6dcaea46  numpy-1.24.3.tar.gz

SHA256

 3c1104d3c036fb81ab923f507536daedc718d0ad5a8707c6061cdfd6d184e570  numpy-1.24.3-cp310-cp310-macosx_10_9_x86_64.whl
 202de8f38fc4a45a3eea4b63e2f376e5f2dc64ef0fa692838e31a808520efaf7  numpy-1.24.3-cp310-cp310-macosx_11_0_arm64.whl
 8535303847b89aa6b0f00aa1dc62867b5a32923e4d1681a35b5eef2d9591a463  numpy-1.24.3-cp310-cp310-manylinux_2_17_aarch64.manylinux2014_aarch64.whl
 2d926b52ba1367f9acb76b0df6ed21f0b16a1ad87c6720a1121674e5cf63e2b6  numpy-1.24.3-cp310-cp310-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
 f21c442fdd2805e91799fbe044a7b999b8571bb0ab0f7850d0cb9641a687092b  numpy-1.24.3-cp310-cp310-win32.whl
 ab5f23af8c16022663a652d3b25dcdc272ac3f83c3af4c02eb8b824e6b3ab9d7  numpy-1.24.3-cp310-cp310-win_amd64.whl
 9a7721ec204d3a237225db3e194c25268faf92e19338a35f3a224469cb6039a3  numpy-1.24.3-cp311-cp311-macosx_10_9_x86_64.whl
 d6cc757de514c00b24ae8cf5c876af2a7c3df189028d68c0cb4eaa9cd5afc2bf  numpy-1.24.3-cp311-cp311-macosx_11_0_arm64.whl
 76e3f4e85fc5d4fd311f6e9b794d0c00e7002ec122be271f2019d63376f1d385  numpy-1.24.3-cp311-cp311-manylinux_2_17_aarch64.manylinux2014_aarch64.whl
 a1d3c026f57ceaad42f8231305d4653d5f05dc6332a730ae5c0bea3513de0950  numpy-1.24.3-cp311-cp311-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
 c91c4afd8abc3908e00a44b2672718905b8611503f7ff87390cc0ac3423fb096  numpy-1.24.3-cp311-cp311-win32.whl
 5342cf6aad47943286afa6f1609cad9b4266a05e7f2ec408e2cf7aea7ff69d80  numpy-1.24.3-cp311-cp311-win_amd64.whl
 7776ea65423ca6a15255ba1872d82d207bd1e09f6d0894ee4a64678dd2204078  numpy-1.24.3-cp38-cp38-macosx_10_9_x86_64.whl
 ae8d0be48d1b6ed82588934aaaa179875e7dc4f3d84da18d7eae6eb3f06c242c  numpy-1.24.3-cp38-cp38-macosx_11_0_arm64.whl
 ecde0f8adef7dfdec993fd54b0f78183051b6580f606111a6d789cd14c61ea0c  numpy-1.24.3-cp38-cp38-manylinux_2_17_aarch64.manylinux2014_aarch64.whl
 4749e053a29364d3452c034827102ee100986903263e89884922ef01a0a6fd2f  numpy-1.24.3-cp38-cp38-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
 d933fabd8f6a319e8530d0de4fcc2e6a61917e0b0c271fded460032db42a0fe4  numpy-1.24.3-cp38-cp38-win32.whl
 56e48aec79ae238f6e4395886b5eaed058abb7231fb3361ddd7bfdf4eed54289  numpy-1.24.3-cp38-cp38-win_amd64.whl
 4719d5aefb5189f50887773699eaf94e7d1e02bf36c1a9d353d9f46703758ca4  numpy-1.24.3-cp39-cp39-macosx_10_9_x86_64.whl
 0ec87a7084caa559c36e0a2309e4ecb1baa03b687201d0a847c8b0ed476a7187  numpy-1.24.3-cp39-cp39-macosx_11_0_arm64.whl
 ea8282b9bcfe2b5e7d491d0bf7f3e2da29700cec05b49e64d6246923329f2b02  numpy-1.24.3-cp39-cp39-manylinux_2_17_aarch64.manylinux2014_aarch64.whl
 210461d87fb02a84ef243cac5e814aad2b7f4be953b32cb53327bb49fd77fbb4  numpy-1.24.3-cp39-cp39-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
 784c6da1a07818491b0ffd63c6bbe5a33deaa0e25a20e1b3ea20cf0e43f8046c  numpy-1.24.3-cp39-cp39-win32.whl
 d5036197ecae68d7f491fcdb4df90082b0d4960ca6599ba2659957aafced7c17  numpy-1.24.3-cp39-cp39-win_amd64.whl
 352ee00c7f8387b44d19f4cada524586f07379c0d49270f87233983bc5087ca0  numpy-1.24.3-pp38-pypy38_pp73-macosx_10_9_x86_64.whl
 1a7d6acc2e7524c9955e5c903160aa4ea083736fde7e91276b0e5d98e6332812  numpy-1.24.3-pp38-pypy38_pp73-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
 35400e6a8d102fd07c71ed7dcadd9eb62ee9a6e84ec159bd48c28235bbb0f8e4  numpy-1.24.3-pp38-pypy38_pp73-win_amd64.whl
 ab344f1bf21f140adab8e47fdbc7c35a477dc01408791f8ba00d018dd0bc5155  numpy-1.24.3.tar.gz
Links

Update pandas from 1.5.3 to 2.0.3.

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

Links

Update pytz from 2022.7.1 to 2023.3.

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

Links

Update wrapt from 1.15.0rc1 to 1.15.0.

Changelog

1.15.0

--------------

**Bugs Fixed**

* When the C extension for wrapt was being used, and a property was used on an
object proxy wrapping another object to intercept access to an attribute of
the same name on the wrapped object, if the function implementing the property
raised an exception, then the exception was ignored and not propagated back to
the caller. What happened instead was that the original value of the attribute
from the wrapped object was returned, thus silently suppressing that an
exception had occurred in the wrapper. This behaviour was not happening when
the pure Python version of wrapt was being used, with it raising the
exception. The pure Python and C extension implementations thus did not behave
the same.

Note that in the specific case that the exception raised is AttributeError it
still wouldn't be raised. This is the case for both Python and C extension
implementations. If a wrapper for an attribute internally raises an
AttributeError for some reason, the wrapper should if necessary catch the
exception and deal with it, or propagate it as a different exception type if
it is important that an exception still be passed back.

* Address issue where the post import hook mechanism of wrapt wasn't transparent
and left the ``__loader__`` and ``__spec__.loader`` attributes of a module as
the wrapt import hook loader and not the original loader. That the original
loader wasn't preserved could interfere with code which needed access to the
original loader.

* Address issues where a thread deadlock could occur within the wrapt module
import handler, when code executed from a post import hook created a new
thread and code executed in the context of the new thread itself tried to
register a post import hook, or imported a new module.

* When using ``CallableObjectProxy`` as a wrapper for a type or function and
calling the wrapped object, it was not possible to pass a keyword argument
named ``self``. This only occurred when using the pure Python version of wrapt
and did not occur when using the C extension based implementation.

* When using ``PartialCallableObjectProxy`` as a wrapper for a type or function,
when constructing the partial object and when calling the partial object, it
was not possible to pass a keyword argument named ``self``. This only occurred
when using the pure Python version of wrapt and did not occur when using the C
extension based implementation.

* When using ``FunctionWrapper`` as a wrapper for a type or function and calling
the wrapped object, it was not possible to pass a keyword argument named
``self``. Because ``FunctionWrapper`` is also used by decorators, this also
affected decorators on functions and class types. A similar issue also arose
when these were applied to class and instance methods where binding occurred
when the method was accessed. In that case it was in ``BoundFunctionWrapper``
that the problem could arise. These all only occurred when using the pure
Python version of wrapt and did not occur when using the C extension based
implementation.

* When using ``WeakFunctionProxy`` as a wrapper for a function, when calling the
function via the proxy object, it was not possible to pass a keyword argument
named ``self``.
Links

Update astroid from 2.11.7 to 2.15.5.

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

Links

Update attrs from 22.2.0 to 23.1.0.

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

Links

Update babel from 2.11.0 to 2.12.1.

Changelog

2.12.1

--------------

Fixes
~~~~~

* Version 2.12.0 was missing the ``py.typed`` marker file. Thanks to Alex Waygood for the fix! :gh:`975`
* The copyright year in all files was bumped to 2023.

2.12.0

--------------

Deprecations & breaking changes
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

* Python 3.6 is no longer supported (:gh:`919`) - Aarni Koskela
* The `get_next_timezone_transition` function is no more (:gh:`958`) - Aarni Koskela

New features
~~~~~~~~~~~~

* CLDR: Babel now uses CLDR 42 (:gh:`951`) - Aarni Koskela
* Dates: `pytz` is now optional; Babel will prefer it but will use `zoneinfo` when available. (:gh:`940`) - ds-cbo
* General: Babel now ships type annotations, thanks to Jonah Lawrence's work in multiple PRs.
* Locales: modifiers are now retained when parsing locales (:gh:`947`) - martin f. krafft
* Messages: JavaScript template string expression extraction is now smarter. (:gh:`939`) - Johannes Wilm
* Numbers: NaN and Infinity are now better supported (:gh:`955`) - Jonah Lawrence
* Numbers: Short compact currency formats are now supported (:gh:`926`) - Jonah Lawrence
* Numbers: There's now a `Format.compact_decimal` utility function. (:gh:`921`) - Jonah Lawrence

Bugfixes
~~~~~~~~

* Dates: The cache for parsed datetime patterns is now bounded (:gh:`967`) - Aarni Koskela
* Messages: Fuzzy candidate matching accuracy is improved (:gh:`970`) - Jean Abou Samra
* Numbers: Compact singular formats and patterns with no numbers work correctly (:gh:`930`, :gh:`932`) - Jonah Lawrence, Jun Omae

Improvements & cleanup
~~~~~~~~~~~~~~~~~~~~~~

* Dates: `babel.dates.UTC` is now an alias for `datetime.timezone.utc` (:gh:`957`) - Aarni Koskela
* Dates: `babel.localtime` was slightly cleaned up. (:gh:`952`) - Aarni Koskela
* Documentation: Documentation was improved by Maciej Olko, Jonah Lawrence, lilinjie, and Aarni Koskela.
* Infrastructure: Babel is now being linted with pre-commit and ruff. - Aarni Koskela
Links

Update black from 23.1.0 to 23.3.0.

Changelog

23.3.0

Highlights

This release fixes a longstanding confusing behavior in Black's GitHub action, where the
version of the action did not determine the version of Black being run (issue 3382). In
addition, there is a small bug fix around imports and a number of improvements to the
preview style.

Please try out the
[preview style](https://black.readthedocs.io/en/stable/the_black_code_style/future_style.html#preview-style)
with `black --preview` and tell us your feedback. All changes in the preview style are
expected to become part of Black's stable style in January 2024.

Stable style

- Import lines with ` fmt: skip` and ` fmt: off` no longer have an extra blank line
added when they are right after another import line (3610)

Preview style

- Add trailing commas to collection literals even if there's a comment after the last
entry (3393)
- `async def`, `async for`, and `async with` statements are now formatted consistently
compared to their non-async version. (3609)
- `with` statements that contain two context managers will be consistently wrapped in
parentheses (3589)
- Let string splitters respect [East Asian Width](https://www.unicode.org/reports/tr11/)
(3445)
- Now long string literals can be split after East Asian commas and periods (`、` U+3001
IDEOGRAPHIC COMMA, `。` U+3002 IDEOGRAPHIC FULL STOP, & `,` U+FF0C FULLWIDTH COMMA)
besides before spaces (3445)
- For stubs, enforce one blank line after a nested class with a body other than just
`...` (3564)
- Improve handling of multiline strings by changing line split behavior (1879)

Parser

- Added support for formatting files with invalid type comments (3594)

Integrations

- Update GitHub Action to use the version of Black equivalent to action's version if
version input is not specified (3543)
- Fix missing Python binary path in autoload script for vim (3508)

Documentation

- Document that only the most recent release is supported for security issues;
vulnerabilities should be reported through Tidelift (3612)
Links

Update certifi from 2022.12.7 to 2023.5.7.

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

Links

Update charset-normalizer from 3.0.1 to 3.1.0.

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

Links

Update codecov from 2.1.12 to 2.1.13.

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

Links

Update coverage from 7.1.0 to 7.2.7.

Changelog

7.2.7

--------------------------

- Fix: reverted a `change from 6.4.3 <pull 1347_>`_ that helped Cython, but
also increased the size of data files when using dynamic contexts, as
described in the now-fixed `issue 1586`_. The problem is now avoided due to a
recent change (`issue 1538`_).  Thanks to `Anders Kaseorg <pull 1629_>`_
and David Szotten for persisting with problem reports and detailed diagnoses.

- Wheels are now provided for CPython 3.12.

.. _issue 1586: https://github.com/nedbat/coveragepy/issues/1586
.. _pull 1629: https://github.com/nedbat/coveragepy/pull/1629


.. _changes_7-2-6:

7.2.6

--------------------------

- Fix: the ``lcov`` command could raise an IndexError exception if a file is
translated to Python but then executed under its own name.  Jinja2 does this
when rendering templates.  Fixes `issue 1553`_.

- Python 3.12 beta 1 now inlines comprehensions.  Previously they were compiled
as invisible functions and coverage.py would warn you if they weren't
completely executed.  This no longer happens under Python 3.12.

- Fix: the ``coverage debug sys`` command includes some environment variables
in its output.  This could have included sensitive data.  Those values are
now hidden with asterisks, closing `issue 1628`_.

.. _issue 1553: https://github.com/nedbat/coveragepy/issues/1553
.. _issue 1628: https://github.com/nedbat/coveragepy/issues/1628


.. _changes_7-2-5:

7.2.5

--------------------------

- Fix: ``html_report()`` could fail with an AttributeError on ``isatty`` if run
in an unusual environment where sys.stdout had been replaced.  This is now
fixed.


.. _changes_7-2-4:

7.2.4

--------------------------

PyCon 2023 sprint fixes!

- Fix: with ``relative_files = true``, specifying a specific file to include or
omit wouldn't work correctly (`issue 1604`_).  This is now fixed, with
testing help by `Marc Gibbons <pull 1608_>`_.

- Fix: the XML report would have an incorrect ``<source>`` element when using
relative files and the source option ended with a slash (`issue 1541`_).
This is now fixed, thanks to `Kevin Brown-Silva <pull 1608_>`_.

- When the HTML report location is printed to the terminal, it's now a
terminal-compatible URL, so that you can click the location to open the HTML
file in your browser.  Finishes `issue 1523`_ thanks to `Ricardo Newbery
<pull 1613_>`_.

- Docs: a new :ref:`Migrating page <migrating>` with details about how to
migrate between major versions of coverage.py.  It currently covers the
wildcard changes in 7.x.  Thanks, `Brian Grohe <pull 1610_>`_.

.. _issue 1523: https://github.com/nedbat/coveragepy/issues/1523
.. _issue 1541: https://github.com/nedbat/coveragepy/issues/1541
.. _issue 1604: https://github.com/nedbat/coveragepy/issues/1604
.. _pull 1608: https://github.com/nedbat/coveragepy/pull/1608
.. _pull 1609: https://github.com/nedbat/coveragepy/pull/1609
.. _pull 1610: https://github.com/nedbat/coveragepy/pull/1610
.. _pull 1613: https://github.com/nedbat/coveragepy/pull/1613


.. _changes_7-2-3:

7.2.3

--------------------------

- Fix: the :ref:`config_run_sigterm` setting was meant to capture data if a
process was terminated with a SIGTERM signal, but it didn't always.  This was
fixed thanks to `Lewis Gaul <pull 1600_>`_, closing `issue 1599`_.

- Performance: HTML reports with context information are now much more compact.
File sizes are typically as small as one-third the previous size, but can be
dramatically smaller. This closes `issue 1584`_ thanks to `Oleh Krehel
<pull 1587_>`_.

- Development dependencies no longer use hashed pins, closing `issue 1592`_.

.. _issue 1584: https://github.com/nedbat/coveragepy/issues/1584
.. _pull 1587: https://github.com/nedbat/coveragepy/pull/1587
.. _issue 1592: https://github.com/nedbat/coveragepy/issues/1592
.. _issue 1599: https://github.com/nedbat/coveragepy/issues/1599
.. _pull 1600: https://github.com/nedbat/coveragepy/pull/1600


.. _changes_7-2-2:

7.2.2

--------------------------

- Fix: if a virtualenv was created inside a source directory, and a sourced
package was installed inside the virtualenv, then all of the third-party
packages inside the virtualenv would be measured.  This was incorrect, but
has now been fixed: only the specified packages will be measured, thanks to
`Manuel Jacob <pull 1560_>`_.

- Fix: the ``coverage lcov`` command could create a .lcov file with incorrect
LF (lines found) and LH (lines hit) totals.  This is now fixed, thanks to
`Ian Moore <pull 1583_>`_.

- Fix: the ``coverage xml`` command on Windows could create a .xml file with
duplicate ``<package>`` elements. This is now fixed, thanks to `Benjamin
Parzella <pull 1574_>`_, closing `issue 1573`_.

.. _pull 1560: https://github.com/nedbat/coveragepy/pull/1560
.. _issue 1573: https://github.com/nedbat/coveragepy/issues/1573
.. _pull 1574: https://github.com/nedbat/coveragepy/pull/1574
.. _pull 1583: https://github.com/nedbat/coveragepy/pull/1583


.. _changes_7-2-1:

7.2.1

--------------------------

- Fix: the PyPI page had broken links to documentation pages, but no longer
does, closing `issue 1566`_.

- Fix: public members of the coverage module are now properly indicated so that
mypy will find them, fixing `issue 1564`_.

.. _issue 1564: https://github.com/nedbat/coveragepy/issues/1564
.. _issue 1566: https://github.com/nedbat/coveragepy/issues/1566


.. _changes_7-2-0:

7.2.0

--------------------------

- Added a new setting ``[report] exclude_also`` to let you add more exclusions
without overwriting the defaults.  Thanks, `Alpha Chen <pull 1557_>`_,
closing `issue 1391`_.

- Added a :meth:`.CoverageData.purge_files` method to remove recorded data for
a particular file.  Contributed by `Stephan Deibel <pull 1547_>`_.

- Fix: when reporting commands fail, they will no longer congratulate
themselves with messages like "Wrote XML report to file.xml" before spewing a
traceback about their failure.

- Fix: arguments in the public API that name file paths now accept pathlib.Path
objects.  This includes the ``data_file`` and ``config_file`` arguments to
the Coverage constructor and the ``basename`` argument to CoverageData.
Closes `issue 1552`_.

- Fix: In some embedded environments, an IndexError could occur on stop() when
the originating thread exits before completion.  This is now fixed, thanks to
`Russell Keith-Magee <pull 1543_>`_, closing `issue 1542`_.

- Added a ``py.typed`` file to announce our type-hintedness.  Thanks,
`KotlinIsland <pull 1550_>`_.

.. _issue 1391: https://github.com/nedbat/coveragepy/issues/1391
.. _issue 1542: https://github.com/nedbat/coveragepy/issues/1542
.. _pull 1543: https://github.com/nedbat/coveragepy/pull/1543
.. _pull 1547: https://github.com/nedbat/coveragepy/pull/1547
.. _pull 1550: https://github.com/nedbat/coveragepy/pull/1550
.. _issue 1552: https://github.com/nedbat/coveragepy/issues/1552
.. _pull 1557: https://github.com/nedbat/coveragepy/pull/1557


.. _changes_7-1-0:
Links

Update docutils from 0.19 to 0.20.1.

Changelog

0.20.1

===========================

Bugfix release. See HISTORY_ for details.

0.20

=========================

.. Note::

Docutils 0.20 is the last version supporting Python 3.7 and 3.8.

* General

- Support Python 3.11 (patch 198 by Hugo van Kemenade).

* Output changes:

HTML5:
 Use dpub-ARIA role "doc-footnote" (instead of ARIA role "note")
 for footnotes.

LaTeX:
 Do not load the `inputenc` package in UTF-8 encoded LaTeX sources.
 (UTF-8 is the default encoding for LaTeX2e since 2018).

* Configuration changes:

- Settings in the [latex2e writer] configuration file section
 are now ignored by the "xetex" writer.
 Place common settings in section `[latex writers]`_.

 .. _[latex writers]: docs/user/config.htmllatex-writers

- New command line setting output_. Obsoletes the ``<destination>``
 positional argument (cf. `future changes`__).

 __ `command-line usage pattern`_

* `utils.find_file_in_dirs()` now returns a POSIX path also on Windows;
`utils.get_stylesheet_list()` no longer converts ``\`` to ``/``.

* docutils/languages/
docutils/parsers/rst/languages/

- Support Ukrainian. Patch by Dmytro Kazanzhy.

* test/coverage.sh

- Removed. Use the coverage.py_ project instead,
 ``coverage run test/alltests.py`` and ``coverage report``.

.. _coverage.py: https://pypi.org/project/coverage/

* tools/

- Moved ``quicktest.py`` to ``tools/dev/``.

* Bugfixes and improvements (see HISTORY_).

.. _output: docs/user/config.htmloutput
Links

Update exceptiongroup from 1.1.0 to 1.1.2.

Changelog

1.1.2

- Changed handling of exceptions in exception group handler callbacks to not wrap a
single exception in an exception group, as per
`CPython issue 103590 <https://github.com/python/cpython/issues/103590>`_

1.1.1

- Worked around
`CPython issue 98778 <https://github.com/python/cpython/issues/98778>`_,
``urllib.error.HTTPError(..., fp=None)`` raises ``KeyError`` on unknown attribute
access, on affected Python versions. (PR by Zac Hatfield-Dodds)
Links

Update importlib-metadata from 6.0.0 to 6.7.0.

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

Links

Update keyring from 23.13.1 to 24.2.0.

Changelog

24.2.0

=======

Features
--------

- Require Python 3.8 or later.

24.1.1

=======

Bugfixes
--------

- Restore support for reading from a config file (with regression test). (638)

24.1.0

=======

Bugfixes
--------

- Avoid logging warning when no config file is present. (635)
- Include all operations in the error message if no operation was supplied. (636)


Improved Documentation
----------------------

- Correct name of macOS backend in README. (637)

24.0.1

=======

Misc
----

-

24.0.0

=======

* 633: Added ``diagnose`` command with basic support.
* 487: Removed ``keyring.backends.OS_X`` module.
* 593: Removed ``keyring.util.properties`` module.

23.14.0

========

* 623: On macOS, warn the user when ``keychain`` property is
indicated, as that value can't be honored (macOS API no longer
supports indicating the target keychain).
Links

Update markdown-it-py from 2.1.0 to 3.0.0.

Changelog

3.0.0

⚠️ This release contains some minor breaking changes in the internal API and improvements to the parsing strictness.

**Full Changelog**: <https://github.com/executablebooks/markdown-it-py/compare/v2.2.0...v3.0.0>

⬆️ UPGRADE: Drop support for Python 3.7

Also add testing for Python 3.11

⬆️ UPGRADE: Update from upstream markdown-it `12.2.0` to `13.0.0`

A key change is the addition of a new `Token` type, `text_special`, which is used to represent HTML entities and backslash escaped characters.
This ensures that (core) typographic transformation rules are not incorrectly applied to these texts.
The final core rule is now the new `text_join` rule, which joins adjacent `text`/`text_special` tokens,
and so no `text_special` tokens should be present in the final token stream.
Any custom typographic rules should be inserted before `text_join`.

A new `linkify` rule has also been added to the inline chain, which will linkify full URLs (e.g. `https://example.com`),
and fixes collision of emphasis and linkifier (so `http://example.org/foo._bar_-_baz` is now a single link, not emphasized).
Emails and fuzzy links are not affected by this.

* ♻️ Refactor backslash escape logic, add `text_special` [276](https://github.com/executablebooks/markdown-it-py/pull/276)
* ♻️ Parse entities to `text_special` token [280](https://github.com/executablebooks/markdown-it-py/pull/280)
* ♻️ Refactor: Add linkifier rule to inline chain for full links [279](https://github.com/executablebooks/markdown-it-py/pull/279)
* ‼️ Remove `(p)` => `§` replacement in typographer [281](https://github.com/executablebooks/markdown-it-py/pull/281)
* ‼️ Remove unused `silent` arg in `ParserBlock.tokenize` [284](https://github.com/executablebooks/markdown-it-py/pull/284)
* 🐛 FIX: numeric character reference passing [272](https://github.com/executablebooks/markdown-it-py/pull/272)
* 🐛 Fix: tab preventing paragraph continuation in lists [274](https://github.com/executablebooks/markdown-it-py/pull/274)
* 👌 Improve nested emphasis parsing [273](https://github.com/executablebooks/markdown-it-py/pull/273)
* 👌 fix possible ReDOS in newline rule [275](https://github.com/executablebooks/markdown-it-py/pull/275)
* 👌 Improve performance of `skipSpaces`/`skipChars` [271](https://github.com/executablebooks/markdown-it-py/pull/271)
* 👌 Show text of `text_special` in `tree.pretty` [282](https://github.com/executablebooks/markdown-it-py/pull/282)

♻️ REFACTOR: Replace most character code use with strings

The use of `StateBase.srcCharCode` is deprecated (with backward-compatibility), and all core uses are replaced by `StateBase.src`.

Conversion of source string characters to an integer representing the Unicode character is prevalent in the upstream JavaScript implementation, to improve performance.
However, it is unnecessary in Python and leads to harder to read code and performance deprecations (during the conversion in the `StateBase` initialisation).

See [270](https://github.com/executablebooks/markdown-it-py/pull/270), thanks to [hukkinj1](https://github.com/hukkinj1).

♻️ Centralise indented code block tests

For CommonMark, the presence of indented code blocks prevent any other block element from having an indent of greater than 4 spaces.
Certain Markdown flavors and derivatives, such as mdx and djot, disable these code blocks though, since it is more common to use code fences and/or arbitrary indenting is desirable.
Previously, disabling code blocks did not remove the indent limitation, since most block elements had the 3 space limitation hard-coded.
This change centralised the logic of applying this limitation (in `StateBlock.is_code_block`), and only applies it when indented code blocks are enabled.

This allows for e.g.

md
<div>
<div>

 I can indent as much as I want here.

<div>
<div>


See [260](https://github.com/executablebooks/markdown-it-py/pull/260)

🔧 Maintenance changes

Strict type annotation checking has been applied to the whole code base,
[ruff](https://github.com/charliermarsh/ruff) is now used for linting,
and fuzzing tests have been added to the CI, to integrate with Google [OSS-Fuzz](https://github.com/google/oss-fuzz/tree/master/projects/markdown-it-py) testing, thanks to [DavidKorczynski](https://github.com/DavidKorczynski).

* 🔧 MAINTAIN: Make type checking strict [](https://github.com/executablebooks/markdown-it-py/pull/267)
* 🔧 Add typing of rule functions [283](https://github.com/executablebooks/markdown-it-py/pull/283)
* 🔧 Move linting from flake8 to ruff [268](https://github.com/executablebooks/markdown-it-py/pull/268)
* 🧪 CI: Add fuzzing workflow for PRs [262](https://github.com/executablebooks/markdown-it-py/pull/262)
* 🔧 Add tox env for fuzz testcase run [263](https://github.com/executablebooks/markdown-it-py/pull/263)
* 🧪 Add OSS-Fuzz set up by DavidKorczynski in [255](https://github.com/executablebooks/markdown-it-py/pull/255)
* 🧪 Fix fuzzing test failures [254](https://github.com/executablebooks/markdown-it-py/pull/254)

2.2.0

What's Changed

* ⬆️ UPGRADE: Allow linkify-it-py v2 by hukkin in [218](https://github.com/executablebooks/markdown-it-py/pull/218)
* 🐛 FIX: CVE-2023-26303 by chrisjsewell in [246](https://github.com/executablebooks/markdown-it-py/pull/246)
* 🐛 FIX: CLI crash on non-utf8 character by chrisjsewell in [247](https://github.com/executablebooks/markdown-it-py/pull/247)
* 📚 DOCS: Update the example by redstoneleo in [229](https://github.com/executablebooks/markdown-it-py/pull/229)
* 📚 DOCS: Add section about markdown renderer by holamgadol in [227](https://github.com/executablebooks/markdown-it-py/pull/227)
* 🔧 Create SECURITY.md by chrisjsewell in [248](https://github.com/executablebooks/markdown-it-py/pull/248)
* 🔧 MAINTAIN: Update mypy's additional dependencies by hukkin in [217](https://github.com/executablebooks/markdown-it-py/pull/217)
* Fix typo by jwilk in [230](https://github.com/executablebooks/markdown-it-py/pull/230)
* 🔧 Bump GH actions by chrisjsewell in [244](https://github.com/executablebooks/markdown-it-py/pull/244)
* 🔧 Update benchmark pkg versions by chrisjsewell in [245](https://github.com/executablebooks/markdown-it-py/pull/245)

New Contributors

Thanks to 🎉

* jwilk made their first contribution in [230](https://github.com/executablebooks/markdown-it-py/pull/230)
* holamgadol made their first contribution in [227](https://github.com/executablebooks/markdown-it-py/pull/227)
* redstoneleo made their first contribution in [229](https://github.com/executablebooks/markdown-it-py/pull/229)

**Full Changelog**: <https://github.com/executablebooks/markdown-it-py/compare/v2.1.0...v2.2.0>
Links

Update markupsafe from 2.1.2 to 2.1.3.

Changelog

2.1.3

-------------

Unreleased

-   Implement ``format_map``, ``casefold``, ``removeprefix``, and ``removesuffix``
 methods. :issue:`370`
-   Fix static typing for basic ``str`` methods on ``Markup``. :issue:`358`
Links

Update more-itertools from 9.0.0 to 9.1.0.

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

Links

Update packaging from 23.0 to 23.1.

Changelog

23.1

~~~~~~~~~~~~~~~~~

* Parse raw metadata (:issue:`671`)
* Import underlying parser functions as an underscored variable (:issue:`663`)
* Improve error for local version label with unsupported operators (:issue:`675`)
* Add dedicated error for specifiers with incorrect `.*` suffix
* Replace spaces in platform names with underscores (:issue:`620`)
* Relax typing of ``_key`` on ``_BaseVersion`` (:issue:`669`)
* Handle prefix match with zeros at end of prefix correctly (:issue:`674`)
Links

Update pathspec from 0.11.0 to 0.11.1.

Changelog

0.11.1

-------------------

Bug fixes:

- `Issue 74`_: Include directory should override exclude file.

Improvements:

- `Pull 75`_: Fix partially unknown PathLike type.
- Convert `os.PathLike` to a string properly using `os.fspath`.

.. _`Issue 74`: https://github.com/cpburnz/python-pathspec/issues/74
.. _`Pull 75`: https://github.com/cpburnz/python-pathspec/pull/75
Links

Update platformdirs from 3.0.0 to 3.8.0.

Changelog

3.5.0

-------------------------------
- introduce ``user_music_dir``

3.4.0

-------------------------------
- introduce ``user_videos_dir``

3.3.0

-------------------------------
- introduce ``user_pictures_dir``

3.2.0

-------------------------------
- add auto create directories optional

3.1.1

-------------------------------
- site_cache_dir use ``/var/tmp`` instead of ``/var/cache`` on unix, as the later may be write protected

3.1.0

-------------------------------
- Introduce ``site_cache_dir``

3.0.1

-------------------------------
- Add ``appdirs`` keyword to package
Links

Update pluggy from 1.0.0 to 1.2.0.

Changelog

1.2.0

=========================

Features
--------

- `405 <https://github.com/pytest-dev/pluggy/issues/405>`_: The new-style hook wrappers, added in the yanked 1.1.0 release, now require an explicit ``wrapper=True`` designation in the ``hookimpl()`` decorator.

1.1.0

=====================

.. note::

This release was yanked because unfortunately the implicit new-style hook wrappers broke some downstream projects.
See `403 <https://github.com/pytest-dev/pluggy/issues/403>`__ for more information.
This was rectified in the 1.2.0 release.

Deprecations and Removals
-------------------------

- `364 <https://github.com/pytest-dev/pluggy/issues/364>`_: Python 3.6 is no longer supported.



Features
--------

- `260 <https://github.com/pytest-dev/pluggy/issues/260>`_: Added "new-style" hook wrappers, a simpler but equally powerful alternative to the existing ``hookwrapper=True`` wrappers.

New-style wrappers are generator functions, similarly to ``hookwrapper``, but do away with the :class:`result <pluggy._callers._Result>` object.
Instead, the return value is sent directly to the ``yield`` statement, or, if inner calls raised an exception, it is raised from the ``yield``.
The wrapper is expected to return a value or raise an exception, which will become the result of the hook call.

New-style wrappers are fully interoperable with old-style wrappers.
We encourage users to use the new style, however we do not intend to deprecate the old style any time soon.

See :ref:`hookwrappers` for the full documentation.


- `364 <https://github.com/pytest-dev/pluggy/issues/364>`_: Python 3.11 and 3.12 are now officially supported.


- `394 <https://github.com/pytest-dev/pluggy/issues/394>`_: Added the :meth:`~pluggy._callers._Result.force_exception` method to ``_Result``.

``force_exception`` allows (old-style) hookwrappers to force an exception or override/adjust an existing exception of a hook invocation,
in a properly behaving manner. Using ``force_exception`` is preferred over raising an exception from the hookwrapper,
because raising an exception causes other hookwrappers to be skipped.
Links

Update pygments from 2.14.0 to 2.15.1.

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

Links

Update pylint from 3.0.0a5 to 3.0.0a6.

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

Links
  • PyPI: https:

@pyup-bot
Copy link
Collaborator Author

Closing this in favor of #712

@pyup-bot pyup-bot closed this Jul 17, 2023
@Hugovdberg Hugovdberg deleted the pyup/scheduled-update-2023-07-03 branch July 17, 2023 14:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant