v2.4.0 was released 2026-02-25 and since then there have been a few small bugs reported and fixed and some new flexibility introduced.
Dependencies
The new flexibility introduced by #1313 and some earlier changes were made so that TopoStats can be used more flexibly as a basis for other AFM packages.
In particular I have been working on AFMSlicer for @LaiaPasquina and as my time working on this draws to a close I would like to make a release to PyPI to make it easier for users to install AFMSlicer / napari-afmslicer.
Currently that is not possible because the change introduced by #1313, which allows the header message when running topostats create-config / afmslicer create-config to be flexible only exists on main and PyPI does not allow publishing of packages that have dependencies that are installed from GitHub repositories. Ergo to publish AFMSlicer / napari-afmslicer to make it easy for @LaiaPasquina and others to install and use requires a new release of TopoStats.
What needs doing?
@ubdbra001 is working on some internal aspects by improving type-hints and there are some recent issues reported related to this (#1335 recorded today). These aren't user facing though so would make little/no difference.
Other changes which I've seen and think would be worth addressing prior to release are...
What other small changes need addressing prior to releasing v2.4.1 and how long might these take?
I think a v2.4.1rc1 release might be workable from AFMSlicer perspective and would allow publishing of AFMSlicer to PyPI whilst allowing this work to be addressed.
Full summary of commits since v2.4.0
v2.4.0 was released 2026-02-25 and since then there have been a few small bugs reported and fixed and some new flexibility introduced.
Dependencies
The new flexibility introduced by #1313 and some earlier changes were made so that TopoStats can be used more flexibly as a basis for other AFM packages.
In particular I have been working on AFMSlicer for @LaiaPasquina and as my time working on this draws to a close I would like to make a release to PyPI to make it easier for users to install AFMSlicer / napari-afmslicer.
Currently that is not possible because the change introduced by #1313, which allows the header message when running
topostats create-config/afmslicer create-configto be flexible only exists onmainand PyPI does not allow publishing of packages that have dependencies that are installed from GitHub repositories. Ergo to publishAFMSlicer/napari-afmslicerto make it easy for @LaiaPasquina and others to install and use requires a new release ofTopoStats.What needs doing?
@ubdbra001 is working on some internal aspects by improving type-hints and there are some recent issues reported related to this (#1335 recorded today). These aren't user facing though so would make little/no difference.
Other changes which I've seen and think would be worth addressing prior to release are...
What other small changes need addressing prior to releasing
v2.4.1and how long might these take?I think a
v2.4.1rc1release might be workable from AFMSlicer perspective and would allow publishing of AFMSlicer to PyPI whilst allowing this work to be addressed.Full summary of commits since
v2.4.0save_image_grainstats()#1309