Prepare release notes for v0.26.0#7967
Closed
lagru wants to merge 9 commits intoscikit-image:mainfrom
Closed
Conversation
I'm not sure if this is something we want to highlight at this point. I'm guessing that we eventually want to adopt `spatch` and remove this custom infrastructure?
The new `scaling` attribute added with this PR isn't really documented properly. I think it was discussed as a nice to have for people looking at the internal implementation? So let's not advertise a feature that's not well documented.
lagru
added
the
📄 type: Documentation
lagru
commented
Nov 29, 2025
| - Add new property ``intensity_median`` to ``skimage.measure.regionprops`` (`#7745 <https://github.com/scikit-image/scikit-image/pull/7745>`_). | ||
| - Refactor fundamental matrix scaling (`#7767 <https://github.com/scikit-image/scikit-image/pull/7767>`_). | ||
| - ``binary_blobs`` now supports a ``mode`` parameter for the Gaussian filter, allowing periodic boundary conditions with ``mode="wrap"`` (`#7909 <https://github.com/scikit-image/scikit-image/pull/7909>`_). | ||
| - Add experimental infrastructure for dispatching to a backend. This API is not stable! (`#7520 <https://github.com/scikit-image/scikit-image/pull/7520>`_) |
Member
Author
There was a problem hiding this comment.
Not sure if we want to advertise this in our release notes. It feels like https://github.com/scientific-python/spatch is probably the implementation that will be adopted long-term.
lagru
commented
Nov 29, 2025
This was referenced Nov 29, 2025
|
will there be a wheel for Python-3.14 on Windows ? |
Member
Author
|
@stonebig this is not the best place to ask this question 😉, but yes ARM wheels for Windows will be included (see 0437c1d). See also the wheels of 0.26.0rc0 on PyPI. |
Member
Author
|
Oh, I'm only now noticing the "3.14" part of your question @stonebig. See #7918 (comment). We are investigating. |
Not all of those items are bug fixes. I'd consider an update to a test's code maintenance.
Member
|
I think these will be re-generated, so is it worth editing? Perhaps edit the source PRs instead. |
Member
Author
|
That's what I did (editing the PR descriptions). But I never meant for changelist's output to be used without review! And I'd really like to have proper quality control for release notes. They are one of the few communication channels with our users that we have. And regardless of that, I'm using this PR as an opportunity to bring up outstanding decisions or problems (for example #7967 (comment)). |
Member
Author
|
After a quick discussion in the meeting right now, we've settled on not merging this PR. Right now our release process doesn't account for a final review of the release notes. I'll look into enhancing docstub in a way that we can prepare the notes even more ahead of time. And I'll think if there's a good way to discuss and review release notes with our current release process. |
mkcor
reviewed
Dec 2, 2025
| - moments_hu doctest should ignore tiny differences (`#7944 <https://github.com/scikit-image/scikit-image/pull/7944>`_). | ||
| - Relax constraints of regionprops multichannel test on MacOS with NumPy & "Accelerate" (`#7942 <https://github.com/scikit-image/scikit-image/pull/7942>`_). | ||
| - Refactor names in Pyodide workflow (`#7959 <https://github.com/scikit-image/scikit-image/pull/7959>`_). | ||
| - Use __doctest_requires__ instead of inline importorskip (`#7966 <https://github.com/scikit-image/scikit-image/pull/7966>`_). |
Member
There was a problem hiding this comment.
I find that these 3 'other' items could belong under 'maintenance...'
| - In ``skimage.morphology``, deprecate ``binary_erosion``, ``binary_dilation``, ``binary_opening``, and ``binary_closing`` in favor of ``erosion``, ``dilation``, ``opening``, and ``closing`` respectively. The binary versions weren't actually significantly faster than their non-binary counterparts and sometimes significantly slower. In the future, we might add optimizations internally to the remaining (general, non-binary) functions for when they're used with binary inputs (`#7665 <https://github.com/scikit-image/scikit-image/pull/7665>`_). | ||
| - Deprecate parameter ``max_cost`` in ``skimage.graph.MCP.find_costs`` which previously did nothing. Use the new parameter ``max_step_cost`` instead (`#7625 <https://github.com/scikit-image/scikit-image/pull/7625>`_). | ||
| - Deprecate parameter ``max_cumulative_cost`` in ``skimage.graph.MCP.find_costs`` which did nothing (`#7625 <https://github.com/scikit-image/scikit-image/pull/7625>`_). | ||
| - Deprecate parameter ``max_cost`` in ``skimage.graph.MCP.find_costs`` which previously did nothing. Use the new parameter ``max_step_cost`` instead (`#7625 <https://github.com/scikit-image/scikit-image/pull/7625>`_). |
Member
There was a problem hiding this comment.
Suggested change
| - Deprecate parameter ``max_cost`` in ``skimage.graph.MCP.find_costs`` which previously did nothing. Use the new parameter ``max_step_cost`` instead (`#7625 <https://github.com/scikit-image/scikit-image/pull/7625>`_). | |
| - Deprecate parameter ``max_cost`` in ``skimage.graph.MCP.find_costs`` which previously did nothing. Use the new parameter ``max_step_cost`` instead (`#7625 <https://github.com/scikit-image/scikit-image/pull/7625>`_). |
| - In ``skimage.morphology.remove_small_objects``, deprecate the ``min_size`` parameter in favor of the new ``max_size`` parameter to make API and behavior clearer. This new threshold removes objects smaller than **or equal to** its value, while the previous parameter only removed smaller ones (`#7739 <https://github.com/scikit-image/scikit-image/pull/7739>`_). | ||
| - Deprecate use of scalar ``scale``, with ``dimensionality=3`` where this can be passed to a geometric transform contructor. This allows us to generalize the use of the constructors to the case where the paraters must specify the dimensionality, unless you mean to construct an identity transform. Add ``identity`` class constructor to all geometric transforms. Make all input parameters to Transform constructors, other than ``matrix``, keyword only, to work around difference in the order of parameters, from the order of application, in ``AffineTransform`` (`#7754 <https://github.com/scikit-image/scikit-image/pull/7754>`_). | ||
| - Deprecate parameter ``num_workers`` in ``skimage.restoration.cycle_spin``; use ``workers`` instead (`#7302 <https://github.com/scikit-image/scikit-image/pull/7302>`_). | ||
| - In ``skimage.transform``, deprecate the use of scalar ``scale``, with ``dimensionality=3`` where this can be passed to a geometric transform contructor. This allows us to generalize the use of the constructors to the case where the parameters must specify the dimensionality, unless you mean to construct an identity transform (`#7754 <https://github.com/scikit-image/scikit-image/pull/7754>`_). |
Member
There was a problem hiding this comment.
Suggested change
| - In ``skimage.transform``, deprecate the use of scalar ``scale``, with ``dimensionality=3`` where this can be passed to a geometric transform contructor. This allows us to generalize the use of the constructors to the case where the parameters must specify the dimensionality, unless you mean to construct an identity transform (`#7754 <https://github.com/scikit-image/scikit-image/pull/7754>`_). | |
| - In ``skimage.transform``, deprecate use of scalar ``scale`` with ``dimensionality=3``, where this can be passed to a geometric transform constructor. This allows us to generalize the use of constructors to the case where the parameters must specify the dimensionality, unless you mean to construct an identity transform (`#7754 <https://github.com/scikit-image/scikit-image/pull/7754>`_). |
| - Deprecate use of scalar ``scale``, with ``dimensionality=3`` where this can be passed to a geometric transform contructor. This allows us to generalize the use of the constructors to the case where the paraters must specify the dimensionality, unless you mean to construct an identity transform. Add ``identity`` class constructor to all geometric transforms. Make all input parameters to Transform constructors, other than ``matrix``, keyword only, to work around difference in the order of parameters, from the order of application, in ``AffineTransform`` (`#7754 <https://github.com/scikit-image/scikit-image/pull/7754>`_). | ||
| - Deprecate parameter ``num_workers`` in ``skimage.restoration.cycle_spin``; use ``workers`` instead (`#7302 <https://github.com/scikit-image/scikit-image/pull/7302>`_). | ||
| - In ``skimage.transform``, deprecate the use of scalar ``scale``, with ``dimensionality=3`` where this can be passed to a geometric transform contructor. This allows us to generalize the use of the constructors to the case where the parameters must specify the dimensionality, unless you mean to construct an identity transform (`#7754 <https://github.com/scikit-image/scikit-image/pull/7754>`_). | ||
| - In ``skimage.transform``, turn all input parameters to transform constructors keyword-only (other than ``matrix``). This avoids confusion due to the positional parameter order being different from the order by which they are applied in ``AffineTransform`` (`#7754 <https://github.com/scikit-image/scikit-image/pull/7754>`_). |
Member
There was a problem hiding this comment.
Suggested change
| - In ``skimage.transform``, turn all input parameters to transform constructors keyword-only (other than ``matrix``). This avoids confusion due to the positional parameter order being different from the order by which they are applied in ``AffineTransform`` (`#7754 <https://github.com/scikit-image/scikit-image/pull/7754>`_). | |
| - In ``skimage.transform``, turn all input parameters into keyword-only transform constructors (other than ``matrix``). This avoids confusion due to the positional parameter order being different from the order in which they are applied in ``AffineTransform`` (`#7754 <https://github.com/scikit-image/scikit-image/pull/7754>`_). |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Checklist
./doc/examplesfor new featuresRelease note
For maintainers and optionally contributors, please refer to the instructions on how to document this PR for the release notes.